Note that only component-s here are what you'd consider "actual" program that you care about, like the DOM/widgets and event handlers. Everything else is there just to fill in the maze of cruft in between your presentation layer and backend (Oh, did I forget to mention you need to code that too? This was only the frontend app).

Remember when you could just add an <input> field, do a jQuery one-liner and you were done?

@cartman82 Remember when you could just add an <input> field, do a jQuery one-liner and you were done?

Or a simple one-line PHP POST check (that didn't work as intended and you had to regex it?) Cos yeah, I do remember that. We uh...kind of sometimes still do that. Because PHP.

It's shit like this that makes me glad not to be a front-end developer. Even though I'm a PHP developer - which, if we were in the army, would make me the private nobody likes that always has to clean the toilets and gets letters home from Mummy about how hard things must be in the army and how she'll always love me even though I was starved of oxygen at birth

@cartman82 Plus most PHP frameworks are reasonably simple - Laravel and CodeIgniter are pretty straightforward to be fair to them without dragging out common functionality and making it harder to use (except for Laravel's Eloquent ORM, fuck Eloquent in the majority of cases)

You can always use Symfony - it's a beast of a framework, but simple stuff can be done in pretty simple ways. For example, adding whole user management (with all the controllers, db, views, etc.) requires one plugin and you're done.

Ok, I lost it there. That's a really good joke! The irony of using ever more grandiose words to describe mundane programming actions ... It's the work of a fine comedian. What will they think of when they need to combine sagas, or have some weird abstraction over sagas where all powerful objects send messages? A mythology?

Lemme guess: it all started out as a simple, sane idea, which was then shoehorned into every possible library and function?

Lemme guess: it all started out as a simple, sane idea, which was then shoehorned into every possible library and function?

They used to have just the reducers. A pyramid of pure functions crystalizing immutable structures into the single application state. It was a real functional programming system. A pure system. The perfect system.

Then someone realised: "Hey, what about when we want to get some actual data into our perfect system. You know, like through... ajax requests?"

Note that only component-s here are what you'd consider "actual" program that you care about, like the DOM/widgets and event handlers. Everything else is there just to fill in the maze of cruft in between your presentation layer and backend (Oh, did I forget to mention you need to code that too? This was only the frontend app).

Remember when you could just add an <input> field, do a jQuery one-liner and you were done?

But sure, go ahead and reimplement the entire browser in JavaScript. That's probably the safest bet

When it comes to creating software platforms, there are basically two approaches:

Include every function a developer might possibly need

Include a small, but fast, set of instructions providing just the bare minimum, so that someone can create a proper library on top of it.

Most platforms start with the first one, but as time progresses people realize the existing functions are not flexible enough to do what they want. So they end up reimplementing most of the platform on top of a small subset. It's inevitable.

But sure, go ahead and reimplement the entire browser in JavaScript. That's probably the safest bet.

TBH the way I see the web going in the future is everyone re-implementing stuff in the browser, either without HTML/CSS (e.g. canvas) or some other technology as people get fed up with dealing with designing applications for the web. so the web browser just becomes a display method for whatever graphical toolkit the site uses.

They're collections of connected (user) stories. Seems to make some sense - perhaps "anthologies" would be a better word?

If you want stupid names, try metaheuristics. It's like they get +50% to their grants to come up with stupid names - ant colony optimization (having nothing to do with ants), annealing (having nothing to do with metal), tabu search (having nothing to do with charades)...