200 MB modern application built on top of Chrome can’t handle a few files.

Emacs from the 70/80s can handle a thousand files. Something is wrong with computers.

[-] best_username_ever@sh.itjust.works 67 points 5 months ago* (last edited 5 months ago)

There’s nothing Tanenbaum could do

Tanenbaum doesn’t seem to mind

Today OP was very dumb and showed his ignorance of the concept "I do whatever I fucking want." Don't be like OP.

people regretting releasing their work under a permissive license

They're free to change the licence of future versions. OP also failed at understanding the concept of licences. He's such a silly moron!

IIRC, it's controlled by the carrier and not encrypted. If that's the case, it's bad. We've been moving away from carriers and internet providers, and got some privacy back by various means. Why would be roll that back?

Try medical software and devices. The requirements and specs are mandatory before doing anything. It’s actually very fun and I have less burnout thanks to this.

Why is the USA the only country to have those problems, AND complain about getting free stuff?

It’s not the old program anymore, and it already leaked a long time ago. It was obvious that the new one wouldn’t be open.

I tried it a long time ago and found out that they were injecting links to their shitcoins inside the web pages. Like, additional links in some web sites.

I’m still dumbfounded that there was not more protests about it because it should never happen.

[-] best_username_ever@sh.itjust.works 128 points 5 months ago

But how can you show them that you bought an overpriced shirt made by a child in Bangladesh?

no-code effort

And we know that the no-code fad was very successful in the past.

With an infinite supply of shitty projects created by “devs” who can’t code, I’ll have a guaranteed job for ever. Thanks AI!

Funny because double-doors fridges are called "American fridges" in France because it’s an American thing.

23

cross-posted from: https://sh.itjust.works/post/19440902

I want to document my debugging sessions in a text file but I don't know if anyone did this before.

I came up with this kind of "language" that is a mix between Markdown and C++, but I still wonder if something equivalent exists already.

// When you click on the button
# [click button]
- A::f()
// - ... other method calls, don't document if you don't need to

# A::f()
// "..." for "parameters" where you don't need the details
- Stuff::g(...)
- Stuff::h(...)

// <Class> is a fake template thing to show the possible types of an object
# <SubStuffA | SubStuffB> Stuff::g(...)
- Stuff::g() {} // empty but I use v/=> for virtual call
  v/=> SubStuffA::g()
  v/=> SubStuffB::g()

# SubStuffA::g()

# SubStuffB::g()

# Stuff::h(...)

I document methods in the order of appearance in the code.

If you have any good idea about a reliable way to document a list of function calls, I'm interested!

12

I want to document my debugging sessions in a text file but I don't know if anyone did this before.

I came up with this kind of "language" that is a mix between Markdown and C++, but I still wonder if something equivalent exists already.

// When you click on the button
# [click button]
- A::f()
// - ... other method calls, don't document if you don't need to

# A::f()
// "..." for "parameters" where you don't need the details
- Stuff::g(...)
- Stuff::h(...)

// <Class> is a fake template thing to show the possible types of an object
# <SubStuffA | SubStuffB> Stuff::g(...)
- Stuff::g() {} // empty but I use v/=> for virtual call
  v/=> SubStuffA::g()
  v/=> SubStuffB::g()

# SubStuffA::g()

# SubStuffB::g()

# Stuff::h(...)

I document methods in the order of appearance in the code.

If you have any good idea about a reliable way to document a list of function calls, I'm interested!

Also gaming on a PC is 40 years old, what do they still have to learn?

"People don’t have money. That’s scary for companies selling expensive products."

view more: next ›

best_username_ever

joined 7 months ago