I think it's a correction, There's multiple levels of interpretation:
1. Don't roll your own crypto
2. Don't roll your own auth strategy
3. Don't Roll your own auth code
4. Don't host your own auth infrastructure.
For the last few years level 4 has been aggressively pushed with a lot of advertising spend to push people towards prohibitively expensive hosted providers. Donning a tinfoil hat for a moment, auth as a service companies have made everything seem substantially more difficult than it is too for simple needs.
Now we're seeing a correction back to 2 and 3 as people way up the risks of SaaS vs just using a easier to manage local library and discovering it's not as scary as it's been made out to be if you follow now fairly well established patterns.
the providers aren't going anywhere, people still need them for a variety of reasons but their time as the default is ending and whether this is good is to be determined.
Only if the software is optimised for either in the first place.
Ton of software out there where optimisation of both memory and cpu has been pushed to the side because development hours is more costly than a bit of extra resource usage.
Pivoting to node support and even more-so rewriting deploy really hurt momentum on top of all those projects. Coming out swinging with 2.0 and then decreasing regions and rewriting the product that makes you money soon after was certainly a choice.
While they’ve been doing that void 0 made a significantly better linter & formatter that can replace eslint, a perfect embrace and extend. Nodes improved and a lot of annoyances have been ironed out (at a user level at least), each passing day the benefits of deno reducing.
Fresh is close to abandonware despite being a framework that could be the middle ground between htmx and js framework insanity with even 1 man-day a fortnight dedicated to it.
JSR seems like it’s going nowhere and only exists to install @std.
This was the final straw for me, if they bounce back in a few years hell yeah I’m in but I’m begrudgingly back to node for now.
“In the interest of quelling rumors and speculation, I can confirm this is the basic idea; lean focus (and definitely not an evil acquisition). It's sadly just unfortunate harsh business realities.”
Hasn't stopped certain parties from doing the same thing as Italy though, the CSIRO being credible really hurt their efforts though, Murdoch press tried & failed to discredit them with ferocity.
Worst part is, even if price comes down I think they further poisoned the idea of nuclear in Australia because their plan was brazenly to keep the coal & gas plants running in the meantime rather than spend money on wind/solar. They didn't even make an effort for their timelines and costs to be remotely believable.
F# also has substantially better type inference so you don't need to write the types out everywhere, type aliases are first class too so you can easily write out some helper types for readability.
You can pipe a monadic type through various functions writing little to no type declarations, doing it nicely is F#'s bread and butter.
In C# version n+1 when the language is supposedly getting discriminated unions for real this time I still don't see them being used for monadic patterns like F# because they're going to remain a menace to compose.
I'll defend her on this one somewhat, Github has no exemption as written and she's doing her job.
It's just another layer in the stupidity of this all that GitHub would be blocked but steam, discord and Roblox are exempt because they're for gaming despite being infamous environments.
---[1]
(1) For the purposes of this Act, age‑restricted social media platform means:
(a) an electronic service that satisfies the following conditions:
(i) the sole purpose, or a significant purpose, of the service is to enable online social interaction between 2 or more end‑users;
(ii) the service allows end‑users to link to, or interact with, some or all of the other end‑users;
(iii) the service allows end‑users to post material on the service;
(iv) such other conditions (if any) as are set out in the legislative rules; or
(b) an electronic service specified in the legislative rules;
----[2]
For the purposes of paragraph 63C(6)(b) of the Act, electronic services in each of the following classes are specified:
(a) services that have the sole or primary purpose of enabling end‑users to communicate by means of messaging, email, voice calling or video calling;
(b) services that have the sole or primary purpose of enabling end‑users to play online games with other end‑users;
(c) services that have the sole or primary purpose of enabling end‑users to share information (such as reviews, technical support or advice) about products or services;
(d) services that have the sole or primary purpose of enabling end‑users to engage in professional networking or professional development;
(e) services that have the sole or primary purpose of supporting the education of end‑users;
(f) services that have the sole or primary purpose of supporting the health of end‑users;
(g) services that have a significant purpose of facilitating communication between educational institutions and students or students’ families;
(h) services that have a significant purpose of facilitating communication between providers of health care and people using those providers’ services.
> Returns a `String` instead of a type which disallows the formulation of the problematic `assertEquals` to begin with.
I'm not sure what the best attribution would be but "Make illegal states unrepresentable" would be a fantastic addition to this list pairing well with "parse, don't validate".
A stricter type would force you to parse the URL and would either fix the error (because cleaning trailing/leading slashes might make sense here) or throw a clear error from the parser.
It can be slightly more verbose when you just want to write a string in your test for convenience but can (and does) save a lot of debugging pain for less trivial cases.
It's not as good as google at knowing where you are (gee I wonder why) but if I search Bahn Mi <my town> the results as good as google. Results for something niche like "Keycaps" are showing lots of local results too (or as local as you can get living outside a capital city in Australia).
In all these examples I feel something must be very wrong with the data model if you're conditionally assigning 3 levels down.
At least the previous syntax the annoyingness to write it might prompt you to fix it, and it's clear when you're reading it that something ain't right. Now there's a cute syntax to cover it up and pretend everything is okay.
If you start seeing question marks all over the codebase most of us are going to stop transpiling them in our head and start subconsciously filtering them out and miss a lot of stupid mistakes too.
NPM isn’t perfect but no, it’s fundamentally self inflicted.
Community is very happy to pick up helper libraries and by the time you get all the way up the tree in a react framework you have hundreds or even thousands of packages.
If you’re sensible you can be fine just like any other ecosystem, but limited because one wrong package and you’ve just ballooned your dependency tree by hundreds which lowers the value of the ecosystem.
Node doesn’t have a standard library and until recently not even a test runner which certainly doesn’t help.
If your sensible with node or Deno* you’ll somewhat insulated from all this nonsense.
*Deno has linting,formatting,testing & a standard library which is a massive help (and a permission system so packages can’t do whatever they want)
Given the quality of some of that combo I’ve seen vomited out, it’s technical dismerit.
I wonder if you’re better off with something critical mass enough that an LLM can correctly write it at all but not trained on mountains and mountains of slop.
Silverblue is great but regular Fedora is worth a look too if you don't want to deal with the teething issues of managing all your dev-tools with Silverblue's immutable setup, granted that was 2 years ago when i tried so thing's might be better now.
Infuriatingly; I have a macbook because a couple years ago I wanted a laptop that just worked while keeping my familiar tools but it really feels like Linux is trending up in polish and macOS on the down with an intersect possibly happening in a couple years.
Leavener example might be genuine tweak because they thought it would be better but it could easily be cheapening of ingredients which is a problem with premade mixes too.
The box might be the same volume but i'd expect most mixes wouldn't taste the same these days either. Any mix with chocolate in particular has had the cocoa quantity + quality reduced to the point I can often barely taste it because it's such a comparatively expensive ingredient.
Who else has family recipes with "can of X"? that can of soup from 50 years ago is not the same as today for the worse. I know one of my parents recipes will be gone forever if the creamed corn they use is discontinued or changes to be like every other brand.
There's something wonderful in only knowing that there's and entire lid angle sensor API in a macbook purely because someone reverse engineered it to make the laptop fart.
I have NextDNS profiles on my phone and PC that block problematic sites, as well as the settings dashboard itself to stop me touching it unless I'm on my tablet.
Absolutely, If premium sorted out all those problems and generally treated creators better i'd have a subscription.
I come to youtube for the *creators*, the actual platform where I have watch history off and use extensions to block the aggressively pushed slop as it currently stands is not something I want to put money towards.
I'm already a patreon to a few creators and have a Nebula subscription; adding it up it's probably slightly more than a premium subscription.
They seem pretty cautious with that unstable flag too.
UUID v7 for example is unstable and one would be pretty confident in that not changing at this stage.
Many unstable functions have less churn than a lot of other “stable” packages. It’s a standard library so it’s the right place to measure twice before cementing it forever.
I believe there is a function of age to some degree, I 100% Assassins creed 2 at 14 and now I have a decade and a half of watching studios remake that goddamn game. They're all trying to make the best practice, safest game they can to reach the widest audience and end up bland with nothing new to offer those of us that have been playing a longer time.
Almost all my favourite titles of the last decade have been smaller titles, even the ones I bounce off I can appreciate them for trying something and missing the mark, there are genuine amazing works of art out there that a large studio simply can't produce.
I don't think the AAA games are 'wrong', to my bewilderment assassins creed sells like crazy each year despite near everyone in my friendship circle tapping out after the pirate one a decade ago, it's just if you play more than a couple things a year you outgrow the 'mainstream' titles.
1. Don't roll your own crypto
2. Don't roll your own auth strategy
3. Don't Roll your own auth code
4. Don't host your own auth infrastructure.
For the last few years level 4 has been aggressively pushed with a lot of advertising spend to push people towards prohibitively expensive hosted providers. Donning a tinfoil hat for a moment, auth as a service companies have made everything seem substantially more difficult than it is too for simple needs.
Now we're seeing a correction back to 2 and 3 as people way up the risks of SaaS vs just using a easier to manage local library and discovering it's not as scary as it's been made out to be if you follow now fairly well established patterns.
the providers aren't going anywhere, people still need them for a variety of reasons but their time as the default is ending and whether this is good is to be determined.