Where is the technology? Is it because they used a computer?
French guy here: I went to court once because the cop lied and needed tickets for his quota. I had all the proofs. The judge basically told me “I don’t give a fuck, you pay.” It’s useless.
A strange source has found a few shitty generated memes. That's not journalism at all.
What’s a cager? I can’t give up my car because I can’t bike to work, buses go way too fast on the highway which is dangerous and illegal, and I don’t earn enough to buy an EV or to relocate near my job.
You must understand that poor people can’t live in the EV utopia right now. Car makers will have to sell small and cheap EVs.
Ori 1 & 2. It’s on sale and I’ve never played it before. It’s a great Metroidvania. Also the music is in Bandcamp so I’ll buy that next.
Granted. 80% of the servers now use Windows, and you broke the internet.
I wonder when I’ll get Natvis support on macOS. Qt is pissing me off at work.
The new Firefox: shopping and advertisements.
My car cost 10k€, the equivalent EV is 20k€. Why don’t I buy more EVs? That’s a mystery, let’s call McKinsey to understand why.
Also let’s double the price of more affordable foreign cars to increase the amount of mystery. Sometimes I wonder if governments do this to make fun of us because it’s so stupid.
So the alternative for millions of people will be universal income if they can’t work anymore. It’s still a good alternative but it won’t sell cars and I’m not sure the economy will be happy about it.
That’s what I don’t understand. They want me to save the world with an EV, and at the same time make it so expensive I can’t afford it.
Movies are shown to the public. It doesn’t mean I can copy them for free.
They forgot Zatoichi by Kitano: https://www.imdb.com/title/tt0363226/
Even when I don’t use it? How is it acceptable?
I hope it’s not 200€ but it’s way higher than what I pay for the gas.
I had a similar experience with boxing. We all suffer together, and anyone who makes an effort deserves to be helped. Strong bros are nice people.
that would limit my own option to make a version of the software and sell it under a more limited license in the future
Nope. As the author you're free to license your stuff however you want. You can use 10 different licenses for 10 clients if you want. You could write a custom version of your application and give a non-free license to a specific client if you want.
The Cuphead OST: https://m.youtube.com/watch?v=eL6uzgw_ifg
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!
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!