Watch AvEs vijeos.
Problems.
No problems. After they are fixed by the meat confusor.
They are solved.
Your tool in a vise.
472 karma · joined March 24, 2021
Problems.
No problems. After they are fixed by the meat confusor.
They are solved.
Your tool in a vise.
I at least got Minix 2 with the printed source code in AST's book. Minix 2 was so annoying on real PC hardware that I had to stick a keyboard repeat rate and delay patch whenever I used it. It was all straightforward and the lab assignments on it were easy because it was built for tinkering rather than efficiency.
My uni replaced FreeBSD as the teaching operating system of choice. They also go rid of Oracle DBMS# for Postgres.
# Many, many moons ago I nearly got Aaron Swartz'ed. This is because I tried browsing "proprietary" docs using a Java-based internet proxy to bypass IP ACLs from my "off-campus" location. It was clearly located in North Korea. Then, the browsing was so slow (like Tor but even worse), I figured: Why not mirror it locally instead? And, what kind of documentation "toilet-paper" police are going to sit there watching interactively or SNORT monitor what happens to "precious" corporate documentation they forced me to use?
This requires training ("pre-training" or guidance from a more omniscient-esque knowledge agent), trial-and-error testing, and feedback to attain mastery (accurate and precise pattern-matching).
Think of it analogous to genetic programming of the olden days:
1) Create an arbitrary model (code that results in answers of "is it safe?" "is it helpful?" etc.)
2) Test it
3) Find parts that work and parts that are broken
4) Mutate mostly the broken parts
5) Repeat until funding runs out
It's better to fail-safe being afraid of something if you don't understand it because life is fragile and many things could eat you/hurt you. And, young ones don't have that same experiences or defenses of full-grown, mature (-ish? because they're parents) adults.
Also, Whole Foods' freeganning is a must for everyone tired of Amazon's insane "convenience" (vulture capitalism) pricing.
I'm thinking about lots of "whoopsie-doodles" for interested parties who might want to hack on these for other purposes.
In the US, for experienced/aware/agile cyclists who ride often and defensively, it's usually safer for them to not wear a helmet because:
i) Vehicles statistically give helmet-less cyclists more space.
ii) Unconscious personal safety anxiety and risk-aversion that comes along with a rational cyclist not wearing a helmet. Something they must never forget.
It's legal to ride bikes on sidewalks here.
When I see for-rent scooters dumped blocking public commons, I stop and throw them in the nearest gutter, dumpster, sewer, or river to hold the companies responsible for their users monetarily.
If I see a pizza-delivery robot going 5 mph in a bike lane, I'm going to kick it to the curb or run-over it. And, I'll make sure everyone else does the same. They can pay bike messengers who need the work rather than being job-stealing, pointless automation assholes.
In the US, why not distribute value, transportation, and land sufficiently so people can have a better basic standard of living? Right now, I'm looking at 1000 homeless people and tents huddling under a highway, while my drunken idiot neighbors shout and dance with glee feet from them in a gentrifying, mixed-use development pool. The people who have just enough have no shame or consideration because their motto is "F U, I got mine."
Breaking tools and getting G-code just right seem like the perpetual headaches of modern machinists. Other than occasionally being bitten by a bitchy blade-like chip begging to fillet your grizzled knuckles one last time before banishment from the bench to the backyard becycling bile of betal bits.
If electricity were cheap (or the electric meter rewindable), would multiple beam concurrent FDM be a consideration if the materials and metallurgical characteristics allowed it? I think at some point, it's easier to print complex shapes additively than machine them subtractively, and that needs to be part of structured cost decision-analysis for manufacturing.
Google Translate didn't work on this site. It just showed a blurred background. https://translate.google.com/translate?sl=nl&tl=en&u=https:/...
----
There was once someone who knew.
It did have a useful purpose at one point for expert users, technicians, and engineers.
A large group came along chanting "What does it mean?" louder and louder until it was a thunderous war-cry.
The one who knew was trying to shout the answer but he was whispering in a tornado.
Then, someone else said loudly: "I don't understand. Let's just get rid of it."
Most everyone said: "Yeah! It's useless!"
No one listened and now that that understanding is lost like the Antikythera mechanism and Damascus steel to the sands of time.
Then some instruments came along that took advantage of lysing cells for analysis: flow cytometry.
If you can look at cells without going full-power Death Star on them, that sounds damn useful.
---
I anticipate Applied Science will build one in his garage over the weekend and apologize for not making it 2 orders-of-magnitude more sensitive than UQ's. :bow before the might of this over-achiever who ships, a hacker as salty as my HP 48G/X:
Cross-platform development will never be improved by N-times duplicated effort of abstraction layers on-top. The best that could happen is for OS developers to agree on common interfaces like UNIX/The Open Group for low-level operations, but for high-level media, UI, and common native development APIs more integrated than a patchwork of libraries like Qt, LibUV, etc.
I've worked on nuclear reactor simulators in F95, embedded industrial GPS equipment, deadline-oriented ad server meta-mediation, Fortune 500 client-facing consulting, compilers, functional programming projects, and now earn a paycheck doing SRE/PE since it's easy money to fund side-hustles.
Simplicity goes too far on the balance of, and in search for, advancement of design. Form + Function. Not an industrial beige box bucket of parts and not a confusing 2001 monolith, but something in the middle.
1. Odds that he was intentionally faking, looking for an attention opportunity.
2. Odds that he believed he was crippled, when he was slowly recovering and the experience incidentally allowed him to "relearn" motor control.
3. Odds that SARS-CoV-2 caused a temporary change in neuromotor control incidentally to damage/remodeling elsewhere.
4. Odds that SARS-CoV-2 caused a permanent change in neuromotor control incidentally to damage/remodeling elsewhere.
An affordance affords. It's in the word.
> pulling, but not pushing.
Because of prior ubiquitous, universal training. Something with a place for fingers to grasp must be for pulling because pushing needs no such requirements.
If you want to split concept hairs or justify common-sense, you're going to have to delve into linguistics.
Have a happy weekend.
Option this, Ctrl that. Yes, they can be discovered socially and informationally, but that goes against intuitiveness.
Windows 95 UI: It might be fuggly, but you know where the bodies are buried.
IKEA: We will show you how to assemble this sawdust into a crappy bookcase that doesn't sit square or level using line drawings and language inconsistently.
FlatUI: Physical products should delivered as a white box inside another white box without instructions. Tech support is an unnecessary expense.
Affordances have a specific meaning in design. Affordances themselves are subjective because they depend on prior user training. Signifiers are nonessential, supportive adjuncts to affordances to reduce cognitive load (fewer uncertainties and more clarity).
"PUSH" sign on a door that already had a door crash bar facing the observer. A crash bar already indicates it is both a door and opens outwards. A further signifier for a clear wall and door would be a faux door-jam around the perimeter of the door so that people can tell where the door is more easily. If a door blends-in completely to a wall, then any indication of it is an affordance.. it's additional, supportive cues that would signifiers. Putting bright orange around a "PUSH" sign or some aspect of an opaque doorway would likely make it a signifier.
If you present me with a blue rectangle on a black screen, it's still confusing and cognitively-loading what the hell it's for or if it does anything. There are no affordances, only questions.
If you present me with a blue rectangle with an outset, stippled border on a black screen, it's clearly a button. Without that border that meshes with familiar previous training, there's no way to know it was a button. That's an affordance.
If a highlight or animation were added to the blue rectangle that already had an affordance, that would be a signifier.
Affordances are major indicators of action potential while signifiers are minor, helpful reinforcers of affordances.
The messy, subjective discussion is: what happens when all signifiers are thrown away, and then affordances too? Baby/bathwater defenestration.
https://ux.stackexchange.com/questions/94265/whats-the-diffe...
Put another way, it may well be some sort of Dunning-Kruger arrogance that the self-esteem crowd foists on the rest of us without our permission.
- DOS 4.0
- Microsoft Bob
- Windows ME
- Windows Vista
- JScript
- MSJVM
- Zune
- Eliminating all/most easter eggs
https://www.infoworld.com/article/2612971/microsoft-s-13-wor...
You can make many, many mistakes as a giant company, so long as they're not fatal. ;-)
Mac and iOS are relatively-straightforward, aren't terribly different, and share development resources.
Android (Kotlin) doesn't often lead to suicidal ideation.
Windows is meh.
Linux is so-so.
> So electron makes plenty of sense to developers
To mostly front-end developers who don't know much about the world outside of a browser.
> , even although it's an egregious resource hog.
Violating nonfunctional requirements to be usable, performant, and efficient.
The reason is that these "cross-platform" applications on top of web browsers are basically complete operating systems emulated on top of the underlying OS. It's worse than turtles all the way down; they're sea urchins: fragile, prickly, and lethargic. And these memory-hogging leviathans multiply faster than rabbits so developers don't have to get their "hands dirty with details" like fast, efficient, proper software.
Just because someone can write a ray-tracer in BrainFuck doesn't mean NVIDIA/AMD/Intel should steer the whole industry to using something impractical because developers get excited about all of the "possibilities."