I have worked for decades, for companies tiny and huge. I have a github account. I write articles about cutting edge techs. You give me some abstract problem to solve that has no bearing on what I do every day. You don't need me, I don't need you.
My first reaction is "Why?" to these types of questions. I work for a small company now: they have things that need to be done. Coding in large enterprises tends to be "coding in the small", with little creativity required and everything spelled out for you.
I spent over a decade developing in Java, from v1.18 to v6+. The last project was a large Spring app for digital inventory.
Java was never a good choice for web development, and the evidence of that was: J2EE + frameworks. J2EE was unmanageable without a framework, and the frameworks themselves were huge and burdensome. And compilation...bleh!
JavaScript is quick and light for whipping up a web application. It's drawback is the lack of static types, but there is TypeScript if you want it (not perfect, but maybe useful). The other drawback is specific to npm: each module contains its own dependencies. That is both good and bad: good, in that you don't have version conflicts; bad in that there are so many libraries there's no hope you can verify the security of your site, especially for less popular modules.
Is the elimination of corporate welfare factored into this? Farm subsidies would seem to offer substantial savings. Out of work farmers would subsist on UBI.
It's what happens when marketing is allowed to drive technological change. "Oh, look! There $$$ to be made if we can convince everyone to switch paradigms! Let's all write articles about how neat it is!"
I spent many years building cross-platform applications using this new-fangled thing called Java.
Then, someone decided it would be great to build web applications in Java. Oh, and use XML as the communications protocol between server and clients. Oh, and transfer not just data, but objects over-the-wire. Then Spring came along to make things "simpler". Like hell.
Node.js, JavaScript (TypeScript if you prefer) and now Electron are all bringing us back to cross-platform nirvana, only this time using the browser/server interface properly, without a bunch of ill-fitting preconceptions carried over from native desktop applications.
It's called a hack. Rather than fix the root problem, just work around it. With enough hacks, you arrive at an unmaintainable legacy system. The you have to build a new one.
AMP is a no JavaScript solution (some scattered applause from the crowd). It's all "declarative", with some vendor-specific components (not sure if you can even write your own).
For simple storefront pages, it might be worth the effort, but you're not going to be able to share a code base with a React/Angular site.
Users demand more sophistication than the 80x40 character-based applications I first wrote starting out. Back then, I could churn out a working departmental application inside of a week, including data tables, using a 4GL.
Who wants to go back to those days? Now we have internet instead of LANs, GUI, events, threads, all sorts of data stores, and layers of abstraction to manage it all. I don't see it getting any simpler.
If some want to slide through life on a meager income, then most developed countries can support the drag. What adds wind to the sails, though, is the freedom for ambitious people to take risks, knowing they're not going to fall all the way to a deep pit should they fail.
Amen, Brother. How on earth do they let such bad ideas percolate to the end user? I still haven't forgiven them for The Registry: want to change an operating system setting? Just remember this simple GUID: 229G-A17B-CC2E-82DD-E1AF-...
Slashdot Mirror
As the financial sector has shown, there's more money to be made shuffling virtual paper around than there is in actually making useful things.
The universe was created yesterday. All your memories are implanted. You are a brain in a bottle.
I have worked for decades, for companies tiny and huge. I have a github account. I write articles about cutting edge techs. You give me some abstract problem to solve that has no bearing on what I do every day. You don't need me, I don't need you.
My first reaction is "Why?" to these types of questions. I work for a small company now: they have things that need to be done. Coding in large enterprises tends to be "coding in the small", with little creativity required and everything spelled out for you.
To be fair, Java is not as bad as COBOL. But I would rather be writing apps than designing elaborate type systems.
If I poke it, does it not bleed?
Anything other than machine instructions is not a programming language.
Wuss.
npm modules?
But not as dead as SNOBOL
...then I'm no longer filled with self-loathing.
I spent over a decade developing in Java, from v1.18 to v6+. The last project was a large Spring app for digital inventory.
Java was never a good choice for web development, and the evidence of that was: J2EE + frameworks. J2EE was unmanageable without a framework, and the frameworks themselves were huge and burdensome. And compilation...bleh!
JavaScript is quick and light for whipping up a web application. It's drawback is the lack of static types, but there is TypeScript if you want it (not perfect, but maybe useful). The other drawback is specific to npm: each module contains its own dependencies. That is both good and bad: good, in that you don't have version conflicts; bad in that there are so many libraries there's no hope you can verify the security of your site, especially for less popular modules.
Is the elimination of corporate welfare factored into this? Farm subsidies would seem to offer substantial savings. Out of work farmers would subsist on UBI.
It's what happens when marketing is allowed to drive technological change. "Oh, look! There $$$ to be made if we can convince everyone to switch paradigms! Let's all write articles about how neat it is!"
That's exactly what Deep Mind wants you to believe, pitiful humans!
They stopped teaching alchemy in schools ages ago, and now look where we are.
I spent many years building cross-platform applications using this new-fangled thing called Java.
Then, someone decided it would be great to build web applications in Java. Oh, and use XML as the communications protocol between server and clients. Oh, and transfer not just data, but objects over-the-wire. Then Spring came along to make things "simpler". Like hell.
Node.js, JavaScript (TypeScript if you prefer) and now Electron are all bringing us back to cross-platform nirvana, only this time using the browser/server interface properly, without a bunch of ill-fitting preconceptions carried over from native desktop applications.
It's called a hack. Rather than fix the root problem, just work around it. With enough hacks, you arrive at an unmaintainable legacy system. The you have to build a new one.
How much money was spent on high-end salaries?
AMP is a no JavaScript solution (some scattered applause from the crowd). It's all "declarative", with some vendor-specific components (not sure if you can even write your own).
For simple storefront pages, it might be worth the effort, but you're not going to be able to share a code base with a React/Angular site.
They=> The
ugh. can't edit in /.
Users demand more sophistication than the 80x40 character-based applications I first wrote starting out. Back then, I could churn out a working departmental application inside of a week, including data tables, using a 4GL.
Who wants to go back to those days? Now we have internet instead of LANs, GUI, events, threads, all sorts of data stores, and layers of abstraction to manage it all. I don't see it getting any simpler.
If some want to slide through life on a meager income, then most developed countries can support the drag. What adds wind to the sails, though, is the freedom for ambitious people to take risks, knowing they're not going to fall all the way to a deep pit should they fail.
Amen, Brother. How on earth do they let such bad ideas percolate to the end user? I still haven't forgiven them for The Registry: want to change an operating system setting? Just remember this simple GUID: 229G-A17B-CC2E-82DD-E1AF-...
It's later than you think. And still too early for Microsoft.
I will make the pointless observation that this was a truly pointless correction.