[-] FizzyOrange@programming.dev 19 points 1 month ago

I don't have a strong opinion on the beta site, but I do know that they need to stop listening to the exact people that killed their site (or allowed it to be killed by AI at least).

Actually they should have stopped listening to them a decade ago. Now is way too late.

[-] FizzyOrange@programming.dev 20 points 7 months ago

Less "best kept secret" more "not very useful so nobody cared to learn about it".

[-] FizzyOrange@programming.dev 19 points 8 months ago

Very easy to install

This has to be a joke.

[-] FizzyOrange@programming.dev 19 points 9 months ago

Why would I hate systemd? It has fixed many of the problems with desktop Linux that many people refused to even admit were problems. This looks like it throws all that away.

[-] FizzyOrange@programming.dev 19 points 1 year ago

Damn straight. I thought bcachefs was a modern filesystem? Why is it case insensitive? Huge red flag.

[-] FizzyOrange@programming.dev 19 points 1 year ago

Technically they do via a footnote... but it's a pretty confusing one at that!

The FLS stood for the "Ferrocene Language Specification". The minimal fork of Rust that Ferrous Systems qualifies and ships to their customers is called "Ferrocene", hence the name. We'll be dropping the expansion and just calling it the FLS within the Project.

So now it stands for... nothing. Bizarre.

[-] FizzyOrange@programming.dev 19 points 1 year ago

It's not hard and fast but:

  • API is the actual interface for the functions, not the implementation. It's possible for one API to be implemented by more than one library.
  • Library is a bunch of code provided together. It might have more specific meaning depending on the language.
  • A package is something you can install. It's pretty much synonymous to library since most packages contain one library.
  • A framework is just a library that dictates a lot about how your app works.

Apart from API they don't really have strict definitions so they'll be used interchangeably and differently depending on the language.

[-] FizzyOrange@programming.dev 19 points 1 year ago

10-14-25

The 10th of Duember?

[-] FizzyOrange@programming.dev 19 points 2 years ago

The C++ standards committee don't see memory safety or UB as a problem. If they did they wouldn't keep introducing new footguns, e.g. forgetting return_void() in a coroutine. They still think everyone should just learn the entire C++ spec and not make mistakes.

[-] FizzyOrange@programming.dev 19 points 2 years ago

Wow, they (apparently) finally made the REPL not suck! I always thought it was weird how shit it was given that it's one of the big reasons Python has become as popular as it is.

Maybe in another 20 years they can make the package tooling not suck too.

[-] FizzyOrange@programming.dev 19 points 2 years ago
def foo(x):
  return x.whatevr

No linter is going to catch that.

[-] FizzyOrange@programming.dev 19 points 2 years ago

Yeah this is one of the main reasons why Stackoverflow's question closing policies are bullshit. We're going to close the question so nobody can answer it... but they can still upvote it and it will still be ranked highly on Google!

Bunch of idiots.

You know the SO Devs actually tried to improve this a while ago - I think you would be able to reopen your question once or something. Of course the power-hungry mods hated that idea and the abandoned it.

At this point it's unfixable. They depend on their unpaid mods and they've already attracted the sort of people you absolutely don't want to moderate a site.

The only hack I've found is that if your question gets downvoted/closed you are allowed to delete it, wait half an hour and ask it again. Much better odds of success than editing the question.

view more: ‹ prev next ›

FizzyOrange

joined 2 years ago