Unfortunately, it died because its very niche and also they couldnt keep up with development of drivers for desktops.. This is even worse today...
263 karma · joined September 20, 2021
Unfortunately, it died because its very niche and also they couldnt keep up with development of drivers for desktops.. This is even worse today...
https://research.google/blog/turbo-an-improved-rainbow-color...
I myself implemented 4 colorize functions for that. Common linear Blue -> Red. Linear Blue -> Red adjusted via Green for visibility. Blue -> Yellow -> Red also linear. And of course Turbo from that blog..
Its cool to design sth from scratch, like its own CPU, but it only makes sense if you really enjoy it.. Except, its waste of time. I myself live in retro computing abit, but it have it limits. Like, I would not go back to prised 6502 CPU. Yeah, it was great, legendary CPU, but if we take a look at even cheap options we can buy and use for hobbie projects, there are plenty of pretty quick and capable 32bit CPUs. Its hard to go below 32bit really.
Dont get me wrong, I pay big respect to demoscene, and what they can achieve on C64 for example :). Uber skilled guys, but this is an art :)
Well, dunno what to say about it to you.. Its indeed sad.
The very same thing start on Earth w/ climate change. Temp raises slowly, more CO2 (and more importantly, CH4) in atmosphere. Temp reises more. Atmosphere is hotter, can absorb more H2O vapors as well. Now, when you start hitting first threshold, hydrates (CH4) will be released from shallow ocean bottoms, more CH4 in atmosphere hotter.. cycle accelerates hitting runaway (exponental growth). KABOOM, earth might be doomed.
Its simplified model, not accounting for huge vulcanos on polar, with might explode and make nuclear winter with will block the heating. Complicated stuff, thats why we need scientists :)
Kids: now downvote it into oblivion :) Like I give a shit...
Most of my tools are TUI really, because its much esier to develop. Code reusability is huge. You wrote some nice interactive TList class? Cool, you can reuse it easly in other TUI projects.
Today world is a bit multitasking, so having TUI based Desktop is very limiting imo. Yeah, distractions.. Thats I think personal thing. I run old OS with 4 virtual desktops because one desktop is not really enough. Desktop 1 is generic. Desktop 2 is work. Desktop 3 is usually some Network Simulations I do. Desktop 2 and 3 usually have their own Xserver running, displaying stuff from remote servers. So, leaving GUI is not an option. Just use it smartly :)
And yeah, I use ViM ether in terminal or gViM (native Win32).
Yeah, they were great in 80s where HW was seriously underpowered. I run minimal IceWM and it looks and works great, and its quick :)
I never touched ReactOS, but I suspect is modern enough to handle LF only too. It was targeting Win2003 AFAIR.
So yeah, I stand corrected abit. If you develop only for windows (especially legacy), use CRLF. Anything w/ portability in mind, go for LF only...
If you develop on windows and only for windows, use CRLF all the way. Just do NOT forget to set .gitattributed correctly, and you are set.
As I said, handling immutable data (incremental) is easy. You just copy and sync. Kinda trival. The problem I had personaly was all the importand docs (and similar) files I work on. First, I wanted snapshots and history, in case of some mistake or failure. Data checksuming, because they are importand. Also, full peer2peer syncing because I have desktop, servers, VMs, laptop, so I want to sync data around. And because I really like GIT, great tool for VCS, I wanted something similar but for generic binary data. Hence I interested in DVFS system. First I wanted full blown mountable DVFS system, but that is complicated and much harder to make it portable.. Repository aproach is easy to implement and is portable (Cygwin, Linux, UNIX, Posix). Works like a charm.
As for downside, If you think git-annex will work for you, just use it :) For me, it was far too complicated (too much moving parts) even for my DVFS usecase. For immutable data is absolutly overkill, to keep 100s of GBs of data there. I just sync :)
Docs and other files you often change is completly different story. This is where DVFS shines. I wrote my own very simple DVFS exacly for that case. You just create directory, init repo manager.. and vioala.. Disk wide VFS is kinda useless as most of your data there just sits..
1) Good content, you like it, you upvote it.
2) Bad content, harmful, misleading, downvote it.
3) Good or ok content, you dont like it, you do NOT downvote it.
The 3th point is most importand. You have right do disagree with someone as someone has right to express his opinion. As long as its not harmful or abusive, you do NOT touch it.
Just keep value sane ;) 4096 or 5120 should be okish.
991k ruby.exe*
I wrote performance monitor in it for fun: http://borg.uu3.net/~borg/?gperf
Now catastrohpic (with I didnt knew at that time) event occured. After 10 years, Internal NIC burnded. I was like, okey.. I have dozens of PCI NICs, lets plug one and vioala. And I did. But, there was problems, after a while (hour or so) I noticed Audio glitches, especially when when there was network activitiy. After more investigation and reading mobo manual I noticed that IRQs were nicely spread for all internal mobo components + PCIe x16 bus. Other PCI ports were always shared one or another. I could do nothing to fix it.
PC now catch dust, I bought used HP 8200 PC with works nice, but its not gaming rig, standard DPC latency is around 2000us, with is quite large.. Still, for normal use that latency is great, Im very sensitive to lag and latency so if I had issues here, I would be mad.
At the end, some pics from my DPC stall fight: