71–80 of 462 posts
Earlier quoted context omitted.
> ...As a developer you need to support this in the future. It might be nice to build today but it will be a nightmare later. But the sort of people choosing a JS stack are quite quick to move on. Make a mess, slap a new achievement on CV and dash.
I don't agree, but I also find your username ironic. Did you dash?
"The simpler product makes it much easier to maintain and scale." This is good news for the developers, the product owners and the customers. I still can't understand why today people choose a (Javascript) stack of build systems, ton of dependencies, and all kinds of exotic tech that is the latest and most hyped. As a developer you need to support this in the future. It might be nice to build today but it will be a n…
Earlier quoted context omitted.
Do we really think Javascript is exotic? Hasn't it proved itself over many years now? That doesn't mean it can't have issues like anything else. And because of the massive scale of the language you'll see a lot of shit. It's a language and ecosystem like anything else - it's what you do with it that matters.
I wouldn't say JavaScript is exotic, it's more to do with what is being done with it. Traditionally it was used to enhance HTML pages with some DOM manipulation but it's now being used for a million other things too. So historically, if your JavaScript code broke your page would still render as it was just html but now there are all sorts of build processes and long chains that use JavaScript to create the html in th…
Of course, you could decide to do something exotic with it (edge rendering, data programming, whatever) but that's not a problem with the language but people wanting to stretch themselves...
"The simpler product makes it much easier to maintain and scale." This is good news for the developers, the product owners and the customers. I still can't understand why today people choose a (Javascript) stack of build systems, ton of dependencies, and all kinds of exotic tech that is the latest and most hyped. As a developer you need to support this in the future. It might be nice to build today but it will be a n…
> Personally I want to build systems. Sure. And so do I. Specifically, I don't want to re build systems that have already been built for me which I can use as dependencies. And I don't want to spend all my time troubleshooting bugs, either - I'll take a well-maintained repository on GitHub with thousands of users bug-testing it for me over some janky thing some guy on another team threw together a few quarters ago be…
Replace this with:
> with thousands of users just like me that once picked it as a dependency and then forgot about the project
WhatsApp is a spy app of Facebook nowadays
Now guess which one they skipped
It always fascinates me how in the engineers' mind it reconciles that their work brings corporations they work for billions and yet they have to rent a tiny apartment for a substantial portion of their salary and otherwise lead a pretty average life. Then going to lavish offices witnessing how the money they could make use of is wasted on vanity.
Earlier quoted context omitted.
That was its fate anyway. Some things just can't really make money unless they do it in scummy ways (or we haven't found a viable alternative or a way to protect them). Public instant messengers, public forums, public file hosting, public image hosting.
With 50 employees their "please pay $1/year" model might have actually made enough revenue