You can run Qwen3 on OVH already:
<https://www.ovhcloud.com/en/public-cloud/ai-endpoints/catalo...>
424 karma · joined February 13, 2015
You can run Qwen3 on OVH already:
<https://www.ovhcloud.com/en/public-cloud/ai-endpoints/catalo...>
I started out with OS/2 v1.1. It had threads, DLLs, multi-tasking, much larger memory space, and from v1.2 a somewhat decent filesystem. Coming from DOS 3.2/Win 2.0 this was an incredible leap, in particular the SDK was amazing compared to the ragtag assembly of info I was used to. The _delta_ between two systems haven't been this large ever since, and I think that is what contributes to the "magic" feeling.
That repository only contains the minified code, not the original source.
<https://www.quora.com/What-is-the-tools-and-languages-used-i...>
The arrangement where the _company_ controls the account seems to me to be more of a allowed delay in salary payout, to the benefit of the company, than a retirement account for the employee.
Some scientific journals, which only provides a Word template, require you to print to PDF to submit, then ships this PDF to India, where a team recreates the look of the submission in LaTeX, which is then used to compose the actual journal. I wish this was hyperbole. For these journals, you can safely create a LaTeX-template looking _almost_ the same, and get away with it.
If one wants an inkjet, I'd go for an Epson EcoTank.
(x === 1) && console.log("it's 1")
Note that you've saved exactly no keystrokes, although this is composable into expressions (if you are using some Javascript-derivative; in ML it would typically already be using the if-form).> People prefer native apps to web apps
> Java has “UI curse”: Looked bad
to be at odds with this aspect of the design:
> No goal to look native
> Leverage Skia
At the same time, this train of though is why VSCode dumps 8 GiB into the ~/.config directory, causing not only a lot longer time to wait for any backup to finish, but also incurring time in getting more and more backup disks, figuring out where to physically store them, etc. Better spend more time up front getting the storage right, and save space and time for those that use it later.
1. A bunch of developers decided to replace the windowing system with something more akin to Desqview.
2. People complained that this now broke their previously working remote desktop.
3. They got told that their use case was utterly unimportant compared to the very pressing issue of getting rid of screen tearing.
4. Upon comments that screen tearing is irrelevant if you don't actually have a desktop, they replied that someone could write a remote desktop extension for Wayland.
5. None of them did.
6. All of the people that actually wanted to get work done stopped listening to them and continued using X11.
Well, until it is, then I frankly hope that Wayland fails and is abandoned, because as it is now it sucks up all the mindshare of desktop Linux into what it consider a dead end: having each and everyone doing their own owner-draw. One can see the same in all these "cross-platform" toolkits that pops up, where all accessibility and themeability has just been thrown out the window (figuratively).
It doesn't matter if "everyone has been doing it like this for the last ten years": That doesn't make it right.