- 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.
- Works fine in AU settings too.
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).
- And more better? I'm not sure either.
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)
- 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.
- 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.
- C# will eventually have unions that will undoubtedly be incompatible too, I worry about source generators becoming ubiquitous as well.
This was also my experience with F#, phenomenal language dragged down by ugly interop with an ecosystem that barely acknowledges its existence and I feel is incompatible with its ideals.
Shame too because there’s some genuinely great stuff in the community like fable [1] where if you were to chuck in JSX like templating you’d have an absolute killer web tool rather than the mess blazor is.
It’s ironic that I found js interop less annoying than .net interop.
- I think I kind of get you, there's something I find off putting about Bun like it's a trendy ORM or front end framework where Node and Deno are trying to be the boring infrastructure a runtime should be.
Not to say Deno doesn't try, some of their marketing feels very "how do you do fellow kids" like they're trying to play the JS hype game but don't know how to.
- Don’t get me wrong, I never meant it was easy to solve, just that things could be better if search parameters didn’t somehow become this niche legacy thing with minimal appetite to fix.
Thanks for the point on RSC, probably the first argument I’ve heard that helps me contextualise why this extreme paradigm shift and tooling complexity is being pushed as the default.
- The JS world leaves me more and more perplexed.There's a similar rant about forms, but why is this so hard? Huge amount of dev time spent being able to execute asynchronous functions to the backend seamlessly yet pretty much every major framework is just rawdog the url string and deal with URLSearchParams object yourself.
Tanstack router[1] provides first class support for not only parsing params but giving you a typed URL helper, this should be the goal for the big meta frameworks but even tools like sveltekit that advertise themselves on simplicity and web standards have next to zero support.
I've seen even non JS frameworks, with like fifteen lines of documentation for half baked support of search params.
The industry would probably be better off if even a tenth of the effort that goes into doing literally anything to avoid learning the platform was spent making this (and post-redirect-get for forms) the path of least resistance for the 90% of the time search params are perfectly adequate.
I don't use HTMX but i do love how it and its community are pushing the rediscover of how much simpler things can be.
[1] https://tanstack.com/router/latest/docs/framework/react/guid...
- It’s only mentioned a couple times outside the title, could be for search engines as I think people still search for core to try and filter out framework results.
I still see it mentioned as core all the time so I didn’t even bat an eye at the title.
I’m not going to blame OP, this entirely on Satan himself who’s been in charge of naming everything at Microsoft for a long time now.
The distinction is useful because .Net framework is certainly still alive.
- The wordiness is a common complaint but TBH it's a minor issue, I do have a growing problem with using tailwind that's hidden just behind that superficial complaint though.
px-3, py-2, bg-red-400 etc. are everywhere in tailwind code and they become more or less undocumented conventions. Technically you can configure them, but practically without unintended side effects on an existing project? And if you make extensive config changes, have you just locked yourself out of the ecosystem?
I don't use bootstrap, but from a brief look at the documentation it seems much more reasonable to diverge from defaults. Looking at themes (https://themes.getbootstrap.com/) it seems more flexible than an average tailwind setup.
- People are maybe a little hyper-fixated on performance.
I have a multi tenanted application dealing with time series data in different time zones and I use Postgres for that.
For a blog and most applications I go SQLite too but I think there’s a good argument that often gets left out that complexity might make Postgres a better choice sometimes even on low traffic.
Between the two I think it is all >90% of us need.
- Personally the problem is just lack of communication. When 2 of your core products look abandoned your inviting this criticism.
I love using Deno, even with the remaining node issues (usually relating to something in the Tower of Babel that is meta frameworks) it’s an exceedingly boring tool which is precisely what I’ve wanted for typescript for years.
I can see they have technical potential but what I want more than anything else right now is just some confidence they’ll be around in 5 years, in this sense I can’t seperate the software and the business as there’s not one without the other.
Hopefully the fresh & deploy v2 updates they’ve been silently working on deliver and this entire concern will evaporate.
- > The odd-numbered .NET releases aren't even worth looking at from an enterprise perspective.
Not hard to argue the opposite either; as you have to upgrade every 2ish years anyway is the LTS track really that valuable compared to updating every march-ish when the latest has been proven? 6 -> 7 -> 8 -> 9 was trivial too.
Meanwhile a friend of mine still has 4.6 going strong and I’d struggle to argue a reason to migrate.
- It’s good software so good luck to them.
.Net OSS looks more and more like a failure, while fans will incessantly reiterate it’s technically OSS it’s certainly not spiritually and if anything it’s regressed in the last 2-3 years.
The bigger project I know of follow a similar model of open core + support and I would not bat an eye if they did the same. The remaining ecosystem seems to be convenience over whatever MS is doing and IO adapters.
At this stage it’s just another nail in the coffin and I’d be wary of picking up anything other than MS packages if using .Net.
I also wonder if eroding confidence will start snowballing and bring .Net back to framework days in practice.
- Deno is perhaps a better example with browser API's, part off the winterTC committee and a growing set of std packages[1].
Possibly more importantly, it has a security model that defends against this kind of exploit.
I will agree with the sentiment though, I get not wanting to jump on new shiny things but for some reason I keep getting the vibe that the community is closer to crab mentality than healthy skepticism, downright hostile towards any project making a genuine effort to improve things.
- I think i'm about a chapter behind you.
I'll add devex extends to TSX/JSX itself too, the editor support and language server experience is miles ahead. Alternative formatters/linters like Deno, Biome, oxc etc. all have great support out of the box too, not so much for svelte.
For when react is a bad match; I'm investigating solid instead for this reason.
The svelte ecosystem is in a particularly unfortunate spot right now comprising of single/few author projects that were starting to stabilise but now have a svelte 4 -> 5 migration shaking things up.
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.