When you spend a significant amount of time working on Linux servers/terminal/CLIs, being forced Windows with "there's WSL for you" answer is so infuriating. It's not the same for so many reasons (networking, disk sharing/speed, tooling, file system pathing quirks to name few).
I worked at a company where I was being denied a Mac despite them being common in the organisation and other engineers had them. I left due to a numerous reasons, and the next-most-senior teammate was very vocal about getting a Mac.
I have been using Java for a good decade now, and it solves all the business problems. Yes, we had an occasional Go/React threat (along JVM-based languages), but I have not seen it coming to a fruition. Java is mature, well supported and understood language that gets regular updates now. Some people don't like it, and that's okay.
What makes JS frameworks so quick to change? Angular, AngularJS, Next, Vue, React, Nue to name the few... What's the urge to reinvent rather than evolve?
young age of developers (average 25-34 years old.), who usually (not always of course) reinvent the wheel because they don't know the past and don't understand the tradeoffs.
Also, it's a way to get attention in this economy of virtue signaling, nobody gives a sh*t if you write a new C++ library that sends rockets into space, it's C++, it's insecure, you should have used Rust.
It's mostly change for the sake of change.
If you're not changing something, you're stuck.
We went full circle a couple times already in the last 30 years, because when you keep turning with no sense of direction, you might end up where you came from.
> What makes JS frameworks so quick to change? … What's the urge to reinvent rather than evolve?
There’s a really low barrier to entry for creating and sharing JS packages. Basically, you can just create a free account on npm and run “npm publish” to make a library available globally for free. Updates are just as easy, and using packages is even easier.
It’s this super low-friction of JS development that drives the ecosystem to constantly iterate. And it even allows solo developers - like ^ this one - to publish and share a new framework.
I haven’t tried to publish packages for Java, Go, Python etc… but I would be very surprised if it’s as easy and unrestricted as npm…
Python is that easy as well, but community tends to focus on libraries rather than frameworks. So there's rarely a splashy site other than docs and less need for evangelism.
If there's two waypoint markers that are named the same, how did the flight control and/or plane software know which one is being referred? Assuming closest, it would have had to special case for it already, no?
e.g. if I want to drive to Springfield, it needs to know which one out of 67 I'd like to go to...
I have no idea about serial adapters, nor I need one. However, the surprising part is that it's only $20. Are they that cheap to make? The R part of R&D must be a lot more, but I assume that's work by an enthusiast rather than a business, hence the price.
Yes wholistically this is probably only looking to cover costs. The low volume maunfacturing may be half that but you end up with so many other costs.
Still many many orders of magnitude simpler then the cheeper PI it plugs in to, which saves enough with scale to be viable.
Back in the day (early 2000s), my classmate had a plan that had a limited bandwidth. That also meant there was a dashboard that you could use to monitor the usage. My classmate clearly didn't like it, because his parents could see when he was playing RuneScape. I had unlimited plan and had no monitoring in place.
So I suggested him he could exceed the limit through downloading some [i]stuff[/i]. Knowing him, he went overboard and racked up a good bill. Think of someone's earnings of working for half a year, full time, at the minimal wage at the time.
ISP didn't budge but they eventually found a way to upgrade to an unlimited plan and drop the bill for going over. Two happy kids...
