I have been stubbornly avoiding 'vi' and have been using 'joe' as my main *nix editor for the past 30 years. Because I cut my computing teeth on Wordstar and Turbo Pascal, and those key sequences are hardwired in my brain.
2,094 karma · joined June 5, 2015
After I started working, I had a hand in selecting Borland C++ as our in-house development platform, and we paid Borland a fortune in licensing fees. Which would have gone to Intel or another company if it were not for my, and other folks in my cohort's experience with pirated Borland products as students.
There is a lesson in there, somewhere.
The same driver was involved in all of the incidents, she was elderly and the vehicle in question was classified "mobility aid", though it looked just like a small car.
I am adamantly of the opinion that any vehicle that shares trails, sidewalks, etc. with pedestrians MUST be speed-limited to walking speed. That includes mobility chairs, scooters, and similar.
Unfortunately, the handicapped community vehemently opposes such speed limits.
Alexa works just about perfectly, setting, unsetting and snoozing alarms as needed. But Google is almost comically incompetent. "Hey google, set an alarm for 4:20 am" -- "Alarm set for 8 pm".
When Alexa starts ringing, I can quietly say "stop" or "snooze". To get Google's attention when it is making noise, both of us have to scream at it more ofte than not.
Keeping them humming along redundantly, with adequate power and cooling, and protection against cooling- and power failures is more of an undertaking, though. Now you are maintaining generators, UPSs and multiple HVAC systems in addition to your 'few racks of servers'.
You also need to maintain full network redundancy (including ingress/egress) and all the cost that entails.
All the above hardware needs maintenance and replacement when it becomes obsolete.
Now you are good in one DC, but not protected against tornadoes, fire and flood like you would be if you used AWS with multiple availability zones.
So, you have to build another DC far enough away, staff it, and buy tons of replication software, plus several FTEs to manage cross-site backups and deal with sync issues.
I thought that colouring the pattern by the instantaneous velocity of the ball would be an obvious improvement and might uncover further structure.
So am I. My first one was written in C in 1995, and the resultant site run under NCSA Httpd. DIY-ing becomes tedious after several cycles, though.
On the other hand, my experience with generally available SSGs has been miserable. They keep breaking my site after a few upgrades. At this point, I am very close to just spinning up wordpress for a new site.
Companies are globally distributed and people spend a LOT of time on conference calls, but most coworking spaces have an open layout that is at best not conducive to conference calls, and often they are not allowed.
I have been working effectively remotely for the past 15 years. Until COVID hit, still commuted to the office, but had very little interaction with local co-workers for actual work. I did appreciate the social aspect, though—water cooler conversations, lunches, company events.
Now that I am fully remote, I would appreciate the opportunity to get out of the house one or two days a week, but I am unable to find a single coworking space that offers private cubicles. They all want you to rent an entire meeting room for conference calls at an exorbitant price.
Doesn't anybody do wirewrap anymore? I, too, struggled with bad connections and crosstalk in my breadboard projects in my first and second year at university, and then I discovered wirewrap, and never looked back.
Apart from having to think in reverse, wirewrap is almost as easy as breadboarding (arguably easier when things get crowded), and it is robust enough to be used for production projects.
If you have 3 of those, you can run a Proxmox cluster, which is a godsend for applications like Home Assistant, which require stability and uptime.
The only time I use a Pi these days is when I need to interface with something via the GPIO pins. Netbooting increases the reliability vastly.
I recall it taking several seconds just to generate the random dot map on my 4.77MHz XT.
... Forge meaningful connections. Ignite your creativity. Elevate your perspective. Redefine your limits. Embrace change. Keep exploring, within and without.
See, it's trivially easy to spout meaningless drivel with the aid of a LLM.
Easy to say flippantly, but my colleagues (let alone my network) are distributed across 10+ countries on four continents. My local 'meatspace' has nothing to offer me career-wise. A professional network needs to be online.
Yes, that is the issue. The finest pen you could likely get would be 0.1mm (and even that would be hard to find and expensive). That is what I based the 250 dpi on.
I don't know about that. Pen plots can, at a push, achieve the equivalent of about 250dpi.
Back in the early 90s, I wrote software for the first inkjet “plotter” (a wide format printer that used HP inkjet cartridges, and rasterized HP-GL commands on the fly). Even back then, we could get 600dpi resolution, and today's printers can do up to 2400 dpi.
I would have thought that autorouting would have improved in all that time, but from this conversation, it sounds like it has become worse. What gives?
Unfortunately, Mozilla decided that this (and other related functionality) is "harmful". https://mozilla.github.io/standards-positions/#webserial
It is a shame, because the overlap between people who use Firefox as their main browser, and people who tinker with microcontrollers is likely pretty large.
Yes, and that is not necessarily a bad thing. Dedicated fans get in first.
At the venue, someone checks your photo, and you scan your ID, which must match the one on the ticket.
But Ticketmaster would never do that, because they make too much money from scalping.