2

Another one bites the dust

 1 month ago
source link: https://changelog.com/news/87
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.

Transcript

šŸ“ Edit Transcript

Changelog

Play the audio to listen along while you enjoy the transcript. šŸŽ§

What up, nerds? Iā€™m Jerod and this is Changelog News for the week of Monday, March 25th 2024.

Thereā€™s a nerdy Pro TipĀ® floating through the series of tubes that you should append before:2023 to your Google searches. This excludes all of the AI-generated ~~content~~ trash thatā€™s been indexed by our computing overlord lately. But thatā€™s amateur hour.

True ProĀ®s append after:2024 to our searches. Want to know who wins the upcoming election?

Ok, letā€™s get into the news.

Redis adopts dual source-available licensing

Another open source project bites the dust. Hereā€™s their explainer:

The success of Redis has created a unique set of challenges. Redis has been sponsoring the bulk of development alongside a dynamic community of developers eager to contribute. However, the majority of Redisā€™ commercial sales are channeled through the largest cloud service providers, who commoditize Redisā€™ investments and its open source community. Despite efforts to support a community-led governance model, and our desire to maintain the BSD license, delivering multiple software distributions simultaneously ā€“ across open source, source-available, and commercial software optimized for different on-premises and cloud platforms ā€“ is at odds with our ability to drive Redis successfully into the future.

When this news first dropped last Wednesday, I quipped: Gentlemen, start your forks. Drew DeVault mustā€™ve been listening. (Probably not literally, but in spirit.) Enter Redict. Drew writes:

Like many of you, I was disappointed when I learned that RedisĀ®1 was changing to a non-free licensing model. This is a betrayal of the free software community, but perhaps not an entirely surprising one. Forks are likely to start appearing in the coming days, and today, I would like to offer Redict to you as a possible future home for your needs, and present its trade-offs as compared to the other forks youā€™re likely to be choosing from soon.

In short, Redict is an independent, non-commercial fork of RedisĀ® OSS 7.2.4.2 It is based on the BSD 3-Clause source code of RedisĀ® OSS, and all changes from this point onwards are licensed under the Lesser GNU General Public license, LGPL-3.0-only.

Oh, and Microsoft also announced Garnet (a Redis client compatible cache-store) just two days prior to the Redis re-licensing. Fortuitous timing or did they know something?

We need community built software

In the wake of this latest open source rug pull, Matthew Miller (Fedora Project Leader at Red Hat) made a great point on Mastodon that I think is worth re-posting in full:

The Redis thing underscores a key point: open source is not enough. We need community built software ā€“ free and open source licenses are just one aspect of that.

If a company requires you to assign copyright (or equivalent re-licensing rights) in an asymmetrical way, they will inevitably eventually decide to take that option once they want to cash in on the goodwill youā€™ve built for them (let alone the code).

This sparked a quality discussion, which you can follow in the replies to his post.

Itā€™s now time for Sponsored News! POST/CON 24 is THE event for API enthusiasts

Postmanā€™s annual user conference pops off April 30th-May 1st in San Fransisco and theyā€™re going all out to ensure this is your must-attend event of the year!

  • Youā€™ll level up your skills with hands-on workshopsā€¦
  • Youā€™ll hear from experts on how theyā€™re bring APIs in to the futureā€¦
  • Youā€™ll be the first to know about new Postman featuresā€¦
  • Youā€™ll help shape the future of Postman by meeting with product leadersā€¦
  • Youā€™ll network and connect with tech leaders from OpenAI, Heroku & moreā€¦

And, to top it all off: theyā€™re throwing an absolutely amazing after party! šŸ•ŗ

Youā€™ll meet at SFā€™s tallest skybar for cocktails, dinner & 360Ā° views of the City and the Bayā€¦ then stroll to nearby August Hall to enjoy drinks, a private bowling alley & a live performance by multi-platinum recording artist T-Pain. How cool is that?!

Register now using the link in the show notes before itā€™s too late!

DuckDB as the new jq

Paul Gross makes the case that DuckDB (like a SQLite geared towards data applications), because it can natively read and parse JSON as a database table, is better than jq for exploring documents. I tend to agree that SQL is easier to reason about than jqā€™s search syntax, which I use just infrequently enough to have to ask ChatGPT every timeā€¦

Iā€™m a programmer and Iā€™m stupid

Anton Zhiyanov has been getting paid to code for 15 years despite being, in his own words, ā€œpretty dumb.ā€

I havenā€™t been diagnosed with any specific medical condition, but my mental capacity is very limited. I find even easier Leetcode problems challenging. Reading about a basic consensus algorithm makes my head explode. I canā€™t really follow complex dependencies in a code base. I canā€™t learn a fancy language like Rust (I tried, but honestly, itā€™s too much). I hate microservices and modern frontends because there are so many moving parts, I canā€™t keep track of them all.

So what does he do about it? Hereā€™s where things get interestingā€¦

I use the simplest mainstream language available (Go) and very basic Python. I write simple (though sometimes verbose) code that is easy to understand and maintain. I avoid deep abstractions and always choose composition over inheritance or mixins. I only use generics when absolutely necessary. I prefer flat data structures whenever possibleā€¦

He goes on, but you get the drift. Anton keeps things incredibly simple. But thatā€™s not dumb. Thatā€™s smart! Which means heā€™s dismantled his own premise. Which might be dumb? ā€¦ I need a breakā€¦

The one about the web developer job market

Baldur Bjarnason chimes in on our collective sense of impending job doom, from the perspective of web developers:

We have the worst job environment for tech in over two decades and thatā€™s with the ā€œAIā€ bubble in full force. If that bubble pops hard before the job market recovers, the repercussions to the tech industry will likely eclipse the dot-com crash.

Donā€™t sugarcoat it, Baldur! Shoot it to us straight. Hereā€™s more on how web media is in free fall and thatā€™s bad for web devs too:

Web media is a major employer, both directly and indirectly, of web developers. If a big part of the web media industry is collapsing, then thatā€™s an entire sector that isnā€™t hiring any of the developers laid off by Google, Microsoft, or the rest. And the people they arenā€™t hiring will still be on the job market competing with everybody else who wouldnā€™t have even applied to work in web media.

This would be bad on its own, if it werenā€™t for the fact that search engine traffic is declining as well. LLM-enabled spam sites are flooding the search engine results which drives down traffic to web media sites in general.

Itā€™s mostly more bad news from here. This one sums his stance up:

Itā€™s reasonable to expect that the job market is unlikely to ever fully bounce back, due to the collapse of web media alone.

Itā€™s also reasonable to expect that the job market might take another sharp turn to the worse because the AI Bubble will run its course eventually. It doesnā€™t matter whether itā€™s a genuine innovation or an overblown yarn-ball of dysfunction and wishful thinking, bubbles end eventually.

Both finding a job and hiring for web development will likely only get harder.

There is a section called ā€œSo, what should I do?ā€ that I recommend all web developers at least take a look at. One sentiment that I will heartily echo here: this is probably as good a time as any to start a business.

That is the news for now, but scan this weekā€™s companion Changelog Newsletter for an additional 12 links to cool new tools Iā€™ve found for your toolbox.

Stay tuned to The Changelog. Our 3rd installment of It Depends ships out later this week! The topic this time: whether itā€™s better for software devs to specialize or generalizeā€¦

Have a great week, leave us a 5-star review if you dig it & Iā€™ll talk to you again real soon. šŸ’š

Changelog

Our transcripts are open source on GitHub. Improvements are welcome. šŸ’š


About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK