2,350 karma · joined April 15, 2013
The tough questions are when one asks about what shadow shapes from a single light can be expected on faces inside a regular voxel grid. That's where it just holds the duck.
I am toying with lighting little voxel grid scene these days, targeting RP2040 and a measly 160x120 px screen and it's crazy how computationally and memory expensive this stuff is.
I am more worried that we do not have that many attempts at rebuilding, because coal and oil are finite. OTOH a slower 2nd iteration might actually work better than this one.
EDIT: meant to reply lower.
Once I am behind the border, I am reinstalling the system with encryption, then proceed to download key material and other important stuff from home over the internet.
I am never letting anyone near my unlocked laptop and if I ever find it turned off e.g. while visiting office toilet, I just assume it has been infected with firmware level rootkit and I am wiping it without decrypting.
If it's removed from my sight during the border check, I assume the same, purchase a new one in a brick-and-mortar shop and sell the infected one when I am back home.
2. Maybe music is actually a hobby and not really necessary to be produced reliably. Maybe the fun is in the negotiation with instruments and people?
If the priority is a diverse, fun, culture, maybe don't structure all economy and politics around the idea forcing people to justify their existence.
Recently another Korean publisher Kakao killed the open source manga reader Tachiyomi.
I wish Hell Joseon would just keep to itself. I wouldn't even miss Samsung at this point to be honest.
Jokes aside, we routinely work for clients without any contract. Contracts get finalized usually by the time a prototype (1/4 - 1/2 of the whole job) is done.
Corporate world is slow. They really like it when you come in and start delivering. Having something to show makes it easier for them to get the project green-lit.
There are obviously some reserves just in case it wouldn't pan out and I still feel quite uneasy. It works, though.
Haha, reminds me that the risk sometimes goes both ways. Like that one time we've got 100% paid for 1/2 the work and then kept working to finish the other 1/2. Can't betray that kind of trust.
(Not related to this drama. Just another data point from elsewhere. It's nice to see others to start working first and only call lawyers second.)
It's a great hobby if you are in it for the actual tech itself. Check out e.g. https://pysdr.org/ for a nice introduction. There is https://www.rtl-sdr.com/ to get you started and https://en.wikipedia.org/wiki/GNU_Radio for more advanced stuff.
You don't need a license to listen!
Also, people are doing some crazy stuff: https://pietern.github.io/goestools/guides/minimal_receiver....
This.
It doesn't matter what the official regime is, as long as the decisions are made by a disconnected committee with no way for the periphery to steer, it's always shit.
You'd have to be blind not to see parallels under capitalism. Employees cannot profit from inventions and improvements, so they don't engage in them. Improving efficiency means budget cuts and animosity from under performers.
This might not be true for smallest companies, but those don't really drive the economy.
You run a vacation home exchange/booking site, which you run in 3 instances in America, Europe and Asia because base you found that people are happier when the site is snappy without those pesky 50ms delays.
Now suppose it's the middle of the night in one of those 3 regions, so no big deal, but the rollout of new version brings down the database that's holding the bookings for two hours before it's fixed. Yeah, it was just the simplest solution to have just a one database with the bookings, because you wouldn't have to worry about all that pesky CAP stuff.
But people then start to ask if it would be possible to book from regions that are not experiencing the outage while double-bookings would still not happen. So you give it a consideration and then you figure out a brilliant, easy solution. You just
> DNS, multi-cast, or some other mechanism directs them towards a healthy load balancer on the healthy side of the partition
Incidentally that's where CAP makes it's appearance and bites your ass.
No amount of VRRP, UCARP wishful thinking can guarantee a conclusion on what partition is "correct" in presence of a network partition between load balancer nodes.
Also, who determines where to point the DNS? A single point of failure VPS? Or perhaps a group of distributed machines voting? Yeah.
You still need to perform the analysis. It's just that some cloud providers offer the distributed voting clusters as a service and take care of the DNS and load balancer switchover for you.
And that's still not enough, because you might not want to allow stragglers write to orphan databases before the whole network fencing kicks in.
The software is updated to contemporary standards and rewritten as people come and go about every 10-20 years. Mandating it to be open source makes it simpler for new vendor to take over in those 10 years. And it might provide other benefits such as some degree of code reuse.
As for the foundational software, there usually is a regional partner of Canonical, SUSE, Red Hat, Microsoft and so on who re-sells the licenses and provides part of the support.
401 = Do I know you?
403 = I can't let you do that, Dave.