119 karma · joined December 20, 2018
This is an anti-union, libertarianism propaganda piece, at best... please don't fall for it.
To sum up: a person whose goals are solely money by any and all means is therefore a criminal: antisocial and unconcerned with others.
Modern MBP's:
- glued-in batteries
- nonservicable RAM
- nonservicable SSD
- lack of peripheral ports
- terrible keyboard
- thin and fragile
- very expensive
- USB-C charging is a step-backwards from MagSafe
- prone to more defects and breakage, and more difficult to repair at the component level, per Louis Rossmann
A1278:
+ older, better keyboard
+ unofficial 16 GiB of third-party RAM
+ 2 SSD's with optical drive removed
+ plenty of ports
+ user-servicable battery
+ MagSafe support
+ relatively lower cost
~ 13" non-Retina display
- thicker
- slower CPU
- slower integrated graphics / GPU
Lenovos:
+ have water-resistant keyboards with drains
+ generally excellent keyboard from IBM lineage
+ 7-10+ hour runtime with both front and rear batteries
+ more normal repair and expansion options
+ semi-rugged
~ moderate cost
- Hackintosh isn't supported nor 100% work-alike
The worst move would be to do what the US is doing:
- nationalist xenophobia turning off expats from emigrating
- exacerbating massive inequality disparity/impoverishing it with people living on highway on-ramp embankment worse than S. American favelas (i.e., go to the Bay Area, drive around.. 'nuf said)
- ban the export of new technology with arms controls, killing industries and making a country radioactive to invest/do business in
- make it extraordinarily difficult for moderately wealthy entrepreneurs to work in a country for even a limited time because their passport isn't from one of a dozen or so favored countries
- ban everyone entirely, regardless of their background or achievements, if they happen to have been born in another set of countries
- double-down on fossil fuels, end clean energy tax credits
To me, the best things from Finland are Linus Torvalds, Jarkko Oikarinen and The Hydraulic Press Channel. There's probably others but the wikipedia page for famous Finns was too long.
I lived with some Norwegians and hung out with YSC in the Bay Area. I'm not more than 10% Scandinavian, if that.
Packing a lunch can be wise, if it's worth your or someone else's time. I spent over $25k/yr dining out for lunch and dinner in my year of maximum unfrugality. :'( Don't do as I did, save money where it balances pennywise (not wasting time saving pennies) and poundwise (not wasting tons of money). At least prepared food from a grocery store rather than a restaurant, meal kit service or restaurant meal delivery service. Take advantage of healthy free or low/er cost food nearby when available. If you're a VC or CEO and raking in coin, pay (almost) any amount to automate everything. If you're broke, automate gradually as you get less broke.
Back to article topic: When I was a kid, every day was a sizable packed lunch from home at school. Had to get to 2 m and 80 kg somehow, as I was two-dimensional until university.
Random error messages
Reboot randomly
Create unusual files
And yet the antivirus can't find anything. :)
BBS lists, Turbo Debugger and that giant purple & white Microsoft Press book with most of the Int 21h calls. Undocumented DOS, Undoc PC and Abrash's books were also helpful. Later, there were good free resources.
Yeah, DOS viruses were bad: booting off an infected floppy, infected HD or running untrusted code was all it took. In Windows, it was worse because autorun would run untrusted code automatically without warning.
There were some darn useful TSR's like Super PC-kwik Power Pak, QEMM and Desqview. Stacker and Doublespace/DriveSpace were kinda slow but did (mostly) work. Stacker had an accelerator card IIRC. And a commercial white bag/gray box mod for Welltris, Mouse Commander, added mouse support to Welltris for DOS by doing some mouse driver to keyboard translation in a TSR that was loaded and unload in a wrapper .BAT file. Many trainers, no-cd/runtime cracks and cheats also used TSR tricks to run.
If someone were broke as in the story, but determined to get life-survival medication no matter what in the US: get rid of all of their property and assets except one vehicle and one house, and get Medicaid. If someone became disabled from a non-work-related condition, there is Medicare SSDI... and they may also qualify for Medicaid. The reason to get rid of property are two-fold: there are maximum qualification limits and bankruptcy would take it. A bankruptcy lawyer costs $2000-4000 FYI.
A is a neutral expression.
B is a somber event where restraint is required: A is appropriate.
B is a happy event or perhaps a close family member: A then B implies he's cold, underwhelmed or disapproving.
B is some random, inanimate object: B holds no new social meaning of A, unless B is symbolic or a plot Macguffin.
It's the same A, but it's the clip B following it that rewrites socioemotional history of the viewer.
At a higher level of abstraction, it and other socioemotional back-rationalizations imply most people allow the future to rewrite their impression of the past, making the past not entirely cast in stone. People can easily turn on each other and then forget about it simply because they choose to rewrite history in their minds, twice.
When something is new or "scary" doesn't mean knee-jerk legislation will do anything other than lead a country to missing out and innovation strengthing other countries.
BE: Go, Erlang/Elixir, Pony, Crystal, Rust... take your pick. REPLs in compiled languages usually have to be faked but are still useful for experimentation. Get used to a good debugger like gdb or lldb, with a convenience layer like Voltron, and profiling tools: dtrace, gperf, valgrind.
BE svcs: EnvoyProxy, Nginx highly-customized, Redis, Postgres, CentOS containerized with Chef, Docker and Habitat... and no Kubernetes. If you have bare metal, OpenStack, pfSense/OpenBSD/NetBSD at the edge, KVM (VMware if you can afford it) and BeeGFS over Ceph. Backup mission-critical data with Tarsnap, others with a mix of S3, Glacier and BackBlaze.
Try to standardize on what works best for the use-case to reduce complexity, iteration time and cost. Develop on what's used in production and follow Twelve Factors methodology generally.
Also, Omni has a cool name logo that almost reminds me of AVID's.
Feel free to add an opinion, I've been evaluating and whittling choices of fonts for code development:
So far Monaco and Source Code Pro seem best.
- Fira Mono https://fonts.google.com/specimen/Fira+Mono
- Hack https://sourcefoundry.org/hack/
- Inconsolata https://fonts.google.com/specimen/Inconsolata
- Monaco http://www.gringod.com/2006/11/01/new-version-of-monaco-font...
- Pragmata Pro https://www.fsd.it/shop/fonts/pragmatapro/
- Source Code Pro https://github.com/adobe-fonts/source-code-pro
I think monospaced, sans-serif, semi/bold, large punctuation and disambiguated look-alikes with antialiasing on works best on a low res laptop. Monospaced serifs seem to look better for code online.
Lower pressure, molten-salt, smaller reactors like DMSR/MSRE @ ORNL and Taylor Wilson proposed with smaller, mass-manufactured reactors with scram/reprocessing pools beneath them would be superior to complex, one-of, inherently riskier, high-pressure *WR.
Disclaimer: I used to work in the nuclear industry in the US until it dried up. Our computer hostnames were based on The Simpsons' characters.
I'm fine with forbiding speech regarding life/safety impact like shouting "fire" and protecting the use of PE for liability and public safety reasons, and letting anyone call themselves a hacker, engineer or whatever else floats their day. To be clear: there ought to be a level of professional rigor where lives are on the line, but otherwise it's caveat hiring manager.
- Microkernel OSes - one driver failing is okay, because it runs in mostly in user-space. The big gotcha in microkernel design is transactions that touch multiple components. Some sort of across-driver transaction API is needed (start, commit, rollback) in order to undo changes across several userspace subsystems.
- A standard language (like the talk suggests) and shipped as portable bytecode to run on a VM or compile to native, so that drivers are portable and runnable without knowing the architecture.
- Devices themselves containing OS-signed drivers rather than each OS having a kitchen-sink installation of all drivers. Each bus would have an interrogation call to fetch the driver.
Two phase flow is a difficult subject, so much so the owner of a nuclear engineering consultancy I worked for wrote his magnum opus on it: Two-Phase Flow in Complex Systems It's imperative to get right in process environments like chemical production facilities and nuclear reactors. https://www.wiley.com/WileyCDA/WileyTitle/productCd-04713296...