arendjr

joined 2 years ago
[–] arendjr@programming.dev 1 points 2 days ago

That’s not just pedantry, that’s unnecessarily narrow-minded. Ever heard of the corrupted heart? According to your definition, that’s an impossibility, unless the heart belongs to someone in authority, or something, I guess.

The point is, there is more than a single interpretation of things, and there is not a singular definition of corruption. Anyone can be corrupted, and giving examples that show that lawlessness permeates every level of society is a great way of showing that corruption is likely endemic in the culture.

[–] arendjr@programming.dev 4 points 2 days ago

I’m Dutch too, and I used to work 8h/day 4 days a week. And my productivity became even better than when I worked 5 days a week. I could kill it those 4 days, and be rested enough the next week so I could kill it again. It worked wonders.

I like the rhetoric, because it means that my employer got something out of it too. But I don’t think it implies that was the only reason it should be given. I obviously enjoyed the time off for my own reasons.

[–] arendjr@programming.dev 8 points 1 month ago

I dunno, I have a Framework laptop and had a keyboard issue with it. It still worked, but one of the keys didn’t register well. So they sent me a new keyboard and I sent them back the old one after I’d swapped it. Not a single day was I without my laptop, which sounds quite unlikely compared to other laptop brands and the support you get (or not) with those. No buyer’s remorse here.

[–] arendjr@programming.dev 6 points 1 month ago

Captchas are getting out of hand.

[–] arendjr@programming.dev 2 points 1 month ago

I can take this one: Because he doesn’t actually care about creating anything of value. If he truly believed in it, you’re right, Twitter or even Tesla’s software engineers would be on the chopping block and he’d replace them with AI as soon as he can. But he doesn’t.

He knows this is a longshot. Most likely to fail, but very profitable on the near-impossible chance that it works. But he doesn’t care even if the odds are truly impossible. Because this is an investment opportunity, so people will throw money his way, no matter what the odds.

People assume he’s an idiot, and he is. But he’s not stupid, at least not in every way. He certainly has a skill for separating others from their money, which he happily takes advantage of.

[–] arendjr@programming.dev 7 points 2 months ago

That’s fair, although technically you could catch SIGSEGV and release resources that way too.

Also, given that resources will be reclaimed by the OS regardless of which kind of crash we’re talking about, the effective difference is usually (but not always) negligible.

Either way, no user would consider a panic!() to be not a crash because destructors ran. And most developers don’t either.

[–] arendjr@programming.dev 4 points 2 months ago (3 children)

“An abrupt exit”, more commonly known as a “crash”.

If you’re going to argue that an exit through panic!() is not a crash, I will argue that your definition of a crash is just an abrupt exit initiated by the OS. In other words, there’s no meaningful distinction as the result is the same.

[–] arendjr@programming.dev 2 points 2 months ago

I don’t understand why you’re getting downvoted. While I don’t share your conviction, I do admit it’s certainly a possibility.

The advantage of doing things that way is that code becomes much more portable. We may finally reach the goal of “write once, run anywhere”, because the AI may write all the platform specific code.

It does make a big assumption that the AI output is reliable enough though. At times people will want to tweak the output, so how are they gonna go about that? Maybe if the language is based on Markdown, you can inject snippets of code where necessary. But if you have to do that too often, such a language will lose its appeal.

There’s a lot of unknowns, but I see why it’s a tempting idea.

[–] arendjr@programming.dev 2 points 3 months ago* (last edited 3 months ago) (2 children)

You know, as a full-time Linux user, I think I rather have game developers continue to create Windows executables.

Unlike most software, games have a tendency to be released, then supported for one or two years, and then abandoned. But meanwhile, operating systems and libraries move on.

If you have a native Linux build of a game from 10 years ago, good luck trying to run it on your modern system. With Windows builds, using Wine or Proton, you actually have better chances running games from 10 or even 20 years ago.

Meanwhile, thanks to Valve’s efforts, Windows builds have incentive to target Vulkan, they’re getting tested on Linux. That’s what we should focus on IMO, because those things make games better supported on Linux. Which platform the binary is compiled for is an implementation detail… and Win32 is actually the more stable target.

[–] arendjr@programming.dev 4 points 3 months ago (1 children)

tsc is (very) slow and there are also no convenient ways to interact with it from Rust.

So it saves a lot development and CI time to roll our own. The downside is that our inference still isn’t as good as tsc of course, but we’re hopeful the community can help us get very close at least.

 

cross-posted from: https://programming.dev/post/32376875

Biome is a formatter and linter for web languages: JavaScript, TypeScript, CSS, HTML, JSON, and GraphQL.

Version 2 adds type-aware lint rules and it is the first TypeScript linter that does not require tsc. Other new features include:

  • Monorepo support
  • GritQL Plugins
  • Revamped, configurable import sorting
  • Linter domains
  • Bulk suppressions
  • Analyzer assists
  • Many new lint rules
 

Biome is a formatter and linter for web languages: JavaScript, TypeScript, CSS, HTML, JSON, and GraphQL.

Version 2 adds type-aware lint rules and it is the first TypeScript linter that does not require tsc. Other new features include:

  • Monorepo support
  • GritQL Plugins
  • Revamped, configurable import sorting
  • Linter domains
  • Bulk suppressions
  • Analyzer assists
  • Many new lint rules
[–] arendjr@programming.dev 10 points 3 months ago (1 children)

I see this argument repeated here every now and then, but it’s not true: https://aoav.org.uk/2020/the-effects-of-strategic-bombing-in-wwii-on-german-morale/

To summarise: Bombing had a profound effect on depressing morale through inducing defeatism, fear and apathy. Bombing did not harden popular resolve against the US. The hate and anger it aroused was directed against the Nazi regime, not the Allies.

 

Biome is an integrated linter/formatter for JavaScript/TypeScript, CSS, HTML and GraphQL.

We are now in the process of implementing TypeScript-like inference (not full type checking!) that allows us to enable type-informed lint rules. This is similar to typescript-eslint except instead of using tsc we attempt to implement the inference ourselves.

This post describes our progress thus far, with a detailed overview of our type architecture.

 

Biome is a formatter and linter for JavaScript, TypeScript and other web languages.

With this partnership, we aim to develop TypeScript-compatible type inference that works out of the box for use in our lint rules.

10
Biome v2.0 beta (biomejs.dev)
submitted 6 months ago* (last edited 6 months ago) by arendjr@programming.dev to c/webdev@programming.dev
 

Biome lead here, so feel free to ask anything!

Biome is an integrated linter and formatter with support for JavaScript, TypeScript, CSS, and more.

Highlights of the release:

  • Plugins: You can write custom lint rules using GritQL.
  • Domains: Domains help to group lint rules by technology, framework, or well, domain. Thanks to domains, your default set of recommended lint rules will only include those that are relevant to your project.
  • Multi-file analysis: Lint rules can now apply analysis based on information from other files, enabling rules such as noImportCycles.
  • noFloatingPromises: Still a proof-of-concept, but our first type-aware lint rule is making an appearance.
  • Our Import Organizer has seen a major revamp.
  • Assists: Biome Assist can provide actions without diagnostics, such as sorting object keys.
  • Improved suppressions: Suppress a rule in an entire file using // biome-ignore-all, or suppress a range using // biome-ignore-start and // biome-ignore-end.
  • HTML formatter: Still in preview, this is the first time we ship an HTML formatter.
  • Many, many, fixes, new lint rules, and other improvements.
 

Recent events in #politics triggered me to write a manifesto on the values of #Democracy and what we can to do preserve them.

 

Biome project lead here, so feel free to ask questions!

 
view more: next ›