uh...yeah... esr is basically Alex Jones if he were half as articulate and twice as ugly.
I read the post because I’m an idiot with too much time to kill. But basically it makes many extraordinary claims, in complete contradiction to reputable sources such as the CDC, supported by likely doctored “evidence” from internet trolls.
Later in the comments see him expertly proclaim that a video on YouTube is evidence of “chorea” which looks nothing like chorea. What a dipshit.
The beauty of the cubicle was in its practical functionality. If you’re working effectice and productively you don’t really notice the plainness of your surroundings.
A private space, but you could still see out the window.
Look, you goofed and misread that comment. The parent said nothing about all BSDs, just “the BSD” which was clearly NetBSD in context. Doubling down just makes you look dumber.
> While the company might give you what you ask for this one time, they will feel blackmalied and will see you as a flight risk, ready to leave for greener pastures at any moment anyway, so they'll prepare themselves by restricting your access to promotions, trainings and critical work so you don't pull that stunt again and slowly reduce its dependency on you
This is a pretty reliable trope. I feel like I hear this every time someone mentions putting the screws to their employer. Yet I have yet to see it borne out by evidence.
It sounds scary. In practice I have never experienced it.
The reality is that institutional memory at most institutions is so fleeting that this above threat has never become an issue in practice.
Mind you in all cases I’ve always been prepared to walk, so that’s something to keep in mind, but I’ve never experienced worse treatment for leveraging what scraps I have. It’s pretty much been the opposite. Once I have that promotion by whatever means, magically I’m treated better. It has never failed.
By flash media do you mean memory cards or SSDs? Because that will be a big difference. The issue might not be the pcie USB adapter, and may be whatever it’s connected to. A cheap usb mass storage chip is not going to perform as well as a uas capable chip.
Nice catch I think. I’ll be damned if I can see a difference. Looks like the old code will also skip the checksum in the case of any non hexdigit padding.
> They also have a lab that do b&w prints from digital files on photo paper interestingly.
Not new or uncommon.
The “last generation” of photo finishing (think drug store 1 hour photo mats) since the early 2000s mostly used digital printers. They called them laser printers no less (not a xerographic process, but direct exposure)
The developed film was scanned and this of course allowed them to give you a CD cheaply. Also of course allowed printing digital media easily.
Yes, pretty much since most ISPs do not block UDP port 53.
I have no reason to run DNS on a home internet connection. What would a sane use case be? They don’t block it because it would be stupid to use it anyway.
Ports that are typically blocked include 67, 139, 161, 520, 547, etc.. ie dhcp, rip, smb, snmp... none of them are any great loss to those that want to run a vpn.
Running a VPN or ssh service is another story and it works fine both TCP and UDP.
> Try running a UDP-only DNS server from home on some random port.
No reason to run DNS.
However, I run openvpn udp between three houses (fios, Comcast, cablevision) for nearly 15 years. It’s pretty common, works fine.
Again in the US... cable, fiber and dsl internet service comes with a public mostly unfiltered IPv4 address, the address is dynamic but in practice it is extremely stable.
End of story.
No idea why you’re acting like such an imbecilic tool in this thread. The whole time I have mentioned that this is the case for major US “landline” ISPs. Yes there are plenty of counterexamples, not sure what point you’re trying to prove.
Almost every ISP will have a firewall of some kind, but in the US this is usually just blocking 25 incoming, sometimes 80 (fios), maybe a few other ports.
I have run services on port 443 on Optimum and FiOS for years.
IP addresses don’t change frequently. Usually what happens is there will be some maintenance and you’ll end up with a new IP because you lost the lease in the interim. If you keep your equipment on though you can have the same reachable IP address for years.
I use a dynamic DNS service so this is rarely a big deal.
Not sure why this is so hard for you to grasp. You keep arguing, for what reason?
Well you either did ask that question and answered it by using appropriate locking and concurrent data structures (which is basically implicitly asking and addressing that question..) or you wrote a lot of crash prone shitty software. Which one was it?
Think of an object oriented system. You can have a thread per object at the extreme where each object has its own thread/queue to handle messages. For most cases with synchronous calls you’re not really getting any concurrency.
Maybe it’s hard to imagine now, but in the 80s and 90s there were people that pushed this sort of architecture with a straight face. Even if not this extreme the idea of using threads for componentization rather than a focus on concurrency..which was possibly a side benefit was very much a thing (think COM/CORBA))
Hence why many articles like this and Ousterhout from the 90s, etc saying it was idiotic.
The bigger problems are more pedestrian like complete lack of suitable IO.