Maybe it's been stated already by someone else here but I really hope that CO2 pricing on the major Cloud platforms will help with this.
It boils down to resources used (like energy) and waste/CO2 generated.
Software/System Developers using 'good enough' stacks/solutions are externalising costs for their own benefit.
Making those externalities transparent will drive alot of the transformation needed.
Kudos! What an impressive collection of features and display of substantial development in almost all areas of the framework!
What's the current status of OpenGl Support? Any progress there? It would be really "cool" and inspiring to be able to develop on older yet otherwise good-enough hardware... thinking about all those very young future devs stuck with all that otherwise good-enough hardware here ;)
We let wgpu https://github.com/gfx-rs/wgpu-rs handle our graphics backend abstraction, so our OpenGL support will come whenever they implement and release it. Currently, it seems to be a WIP.
Please share what that hardware is. On Linux, Vulkan support starts at Intel IvyBridge, which is 8 years old now. Do people develop games on older computers these days? On other OSes, we have D3D12/D3D11 and Metal support.
1. Is there a name/"standard" for the format gron is transforming json into?
2. Thesis:
jq is cumbersome when used on a json input of serious size/complexity because upfront knowledge of the structure of the json is needed to formulate correct search queries.
Gron supports that "uninformed search" use-case much better.
Prove me wrong ;)
1. There isn't really a name for it, but it's a subset of JavaScript and the grammar is available here specified in EBNF, with some railroad diagrams to aid understanding: https://tomnomnom.github.io/gron/
2. That's pretty much exactly why I wrote the tool :)
- A little off-tangent maybe, but are there other professions where this kind of once important but today less important (as some claim) knowledge exists? Is this kind of "knowledge degradation" common in other industries?
- On a different note: how much of mem-space bloat can be attributed to this low-level neglect? Which of course is partly caused by modern languages / programming paradigms abstracting away this low level details for sake of higher level abstractions (which only seldom break, right ;)
- honorable exception: erlang bit-level pattern matching and all the power that comes with it. Btw. did any other language/lib even try to imitate that feature?
Just one more shinny, almost perfect PR reaction... after the fact actually facts which "just incidentally?" helped the sales of newer/replacement products?
That does neither give money back to ppl. who actually replaced their phones for big bucks "because it was slow" nor undoes the unnecessary waste, tactics like this produce, in which waste I guess the Management-Team of the company would not like their children to play in.
We know, we know totally unintended... "the corporation" says after being caught.
U
It's simple: gauge your internal enterprise tendencies towards the right-thing-to-do-by-default (in some countries by-the-law btw) or pay up big time.
It's new kind of mass-market tech news too; vw and other car makers, now apple, many more to come:
very nasty tricks we benefit(ed) from and got caught doing.
Sure.
Sharing mostly the same view of this (hi)story... but: did those guys leave? lost their muses? What happened besides maturing and "standards"-lockdown... outside of some smaller bubbles and marketing gigs the whole eco-system seams stagnant and mostly irrelevant to today's internet/web development... despite so obvious interest of the company.
What happened? What did not happen? (besides mono and unity)
I agree on the first 3... and most probably that's why I very strongly disagree on the last part.
The way the languages "match" the environment in the first 3 examples is almost reciprocal to the way the language is a mismatch in the last one... "it just happened".
Also seeing those first 3 environments even listed with the last one somehow does not seem fitting... but is still a nice pictures of current "Zeitgeist" of computing and software development, imo.
Thinking about "the stack", runtimes , development processes and the root-causes involved here i think, the best thing that could happen to "the industry" is some event preventing the silicon production to deliver new cpu-s/ram/gpu-s/harddrives for some 5+ years or so.
Constrain the resources to bring brack some sane levels of efficiency regarding ram/cpu-cycles/hd-space.
Okay, pure anecdotal but: exactly the same "complaint" including exactly the same advice (minus the "web" ) could be found some 20 years ago. Not only it seems the field is not "structurally" changing much, it seems people are people, still ;) ... and "CRUD" moved to the web.
Yes there has always been demand for what today is the archetypical web app. Data input. Data washing, data into DB, data out of DB data presentation. Basically the same CRUD we do in webapps, but just a DOS interface, VisualBasic form... That's what you don't want to do.
Btw: what's the best source for these kind of one of a kind, contra-intuitive algos and datastructures? Be it online, be it books...
BWT can't be the only one, right?