it is very important to also remind - no amount of alcohol is ever prescribed or sold in the pharmacies. the alcohol was legalized in order to a) reverse the ill effects of prohibition which led to birth of large-scale organized crime; b) to allow regulation of substances innit, as people were dying from bad booze.
likewise, nations may have to legalize in order to regulate the contents of whatever-white-powder users may stumble upon on the street. and let us be honest - no bombs can stop the Fentanil (or rat poison for all I care) from being mixed in.
Yes, because if you're a hardcore liver-failure-in-three-years alcoholic, quitting cold turkey will kill you, and if you're in the hospital for some other issue, they will make sure you get some alcohol.
Doctors don't prescribe it to people who aren't already putting away 50 drinks a week.
I like your point that doctors prescribe things that are necessary to patients, alcohol is one of those things, and there are clear and well-understood examples of when it is medically necessary for a doctor to prescribe and administer alcohol to a patient.
I can bet they quite more often prescribe marijuana, or if you like - CBD or even THC in some cases. And historically, I've been told, the amount of morphine prescribed quite outpaces the alcohol prescriptions, right?
I believe ethanol is not actually often given as an antidote for methanol poisoning in modern times. It does work as a competitive inhibitor of alcohol dehydrogenase (i.e. occupying the enzyme to convert ethanol to acetaldehyde, slowing the conversion of methanol to formaldehyde and on to formic acid, which is not eliminated quickly and causes metabolic acidosis) - allowing the methanol time to leave the body through excretion, and limiting formic acid levels. However, other drugs like fomepizole also inhibit alcohol dehydrogenase with lower toxicity than ethanol.
incredible, isn't it, that no single usable e-paper device is being sold. like no Mac with e-ink, no Surface with e-ink, no ASUS with e-ink, even though this is the best thing an operator can do to his tired eyes.
I'd wager that the whole modus operandi for desktop environments is not made with e-ink in mind.
E-ink fits in a situation where only a few updates are ever required, and completely breaks down for anything requiring higher framerates.
The market might just not be big enough to warrant creating a product.
> the whole modus operandi for desktop environments is not made with e-ink in mind
It used-to be in the DOS and terminal days, and it wouldn't take much to get us back there. Shut off all the eye-candy transition effects. Make your web browser, PDF viewer, etc., always scroll a full page at a time, instead of scrolling 1mm when you click on the button or use the mouse wheel. Just those few changes and you'll have something that'll work pretty well.
Besides, even during DOS days, and generally console days, software such as DB2, Oracle, and all the OS/360 offering, was doing absolutely okay. With all the UTF glyphs available to us now (not to mention the chat interface), I can totally imagine super useful and distraction-less TUIs to front business systems. And e-ink/e-paper would suffice most use-cases for the software which brings actual value to industries.
It's not usual for PC, but if you select "remove animation" on Android you're good on 2 fps. Many applications do like crap as the first placeholders are given little attention, but there are only big refreshes, and only handful of apps written so bad that they ignore the setting and make animated placeholder.
The only thing is that you need to stick to Page Up/Page Down for scrolling.
well mine still does leave a trace, because you know - remote desktop glitters now and then, and particularly if you happen to self-host. also with multi-monitors and heavy window use it makes sense to have trails, than not to.
so the old is not so old, and the new is not dramatically new.
I have one of these. It's only 'ok'. There is significant ghosting and it's not very good when the scene is dark, but it's much better than my BOOX tablet. I just got it so I'm still experimenting with different uses.
It functions like a normal monitor. It connected to my Macbook air (M2) and Windows machine without installing anything. It has a USB-C video port, but an HDMI->USB-C converter works too. It has an 1872x1404 (4:3) resolution, which is why I used Miami Vice for the video. It would not connect to my PS5, which I think comes down to the PS5 only supporting 16:9/21:9.
It's specifically says no Linux support. It seems to me that excludes a large portion of tinkerers and those willing to accept the downsides of bleeding edge technologies, which is probably also their target market. Such as me.
CWM or any light WM could perfectly fit. Once you either use terminal tools or ancient Motif applications (or QT with no animations at all), everything looks usable. Forget Gnome 4 or Plasma with all the bells and wistles on.
It could be sold without any dedicated software, and let the community come up with the interface. Just an LVDS display that fits a widely available Thinkpad would do it.
indeed i should've said "save for some smart tablet offerings such as PineNote and Re:Markable". but these are not so useful for data operators, unless keyboard via bluetooth etc.
I think this is the official J implementation as it stood in 1990 when this paper was originally published, it kept being developed but not this document which describes it. Perhaps someone else knows these details?
There is a relatively recent episode of the ArrayCast array language podcast with Henry Rich who is the primary maintainer and developer of J, talking about new features: https://www.arraycast.com/episodes/episode104-j96
Click on the show notes and there are links to previous episodes with him, talking about the J engine implementation, updates in J 9.03, threading and faster bignum calculations in J 9.04, updates in J 9.5, his views on tacit programming, etc.
It is amazing Nokia missed on the mobile revolution as n900 predated iPhone if I remember correctly.
But Nokia did one massive mistake and it was to bet on Linux for this device. Even when they already had lot of Symbian experience, which also was week though when it came to user apps.
The modified BSD on the first iPhones was simply blazingly fast.
Linux was not a mistake on these devices. And I say that as the foremost hater of open source and Linux you can find around here. In fact, the N9 Linux phone was a huge success among everyday people in several countries. Farmers, teenagers, everybody got an N9. You couldn't go to any small party without at least two people having the N9 phone. Everybody loved them. It was in no way a hacker device for nerds.
What killed these Linux phones was Microsoft doing a hostile takeover of Nokia. The owners of Nokia felt they couldn't compete with Apple's iPhone and decided to scuttle their business and transfer out as much money as possible to their own offshore accounts in the Pacific before the company going belly up. I think they could have competed if they weren't such cowards.
Microsoft did take over Nokia much later than the N900. In fact, Nokia lost value after iPhone showed, and it is only when MS could take over it. And the Android is a side effect of the fact that the .NET was not ready to run existing phones, and Microsoft decided to release the WindowsPhone as non-Nokia branded one.
My BSD statement stays, though, MS did some very good work with the WinPhones, and in fact they were super snappy and useful, very close to what iPhones were at the time. And let's not forget, that the flat looks of (not sure which macos) was directly influenced by these winphones...
N9, not N900. Microsoft took over right before the N9 launch and instantly discontinued any further support for the platform. The "burning platform" as Elop called it.
> You couldn't go to any small party without at least two people having the N9 phone. Everybody loved them. It was in no way a hacker device for nerds.
I don't think I ever saw N9 or any of the N9XX phones in real life.
BSD and Linux are the same thing. That's the whole point of Posix.
What made the difference for the iPhone was that Apple's most expensive part of the whole device was the design. At the point it came out they had something like 23 years of very high end UX under their collective belts. It's one of the reasons why the little 128k Mac that came out the same year as the clunky old IBM PC AT was so expensive, too.
Good design is expensive, and it's the most important thing you'll spend money on.
Remember earlier in the week, all the discussion of Damn Small Linux and how a lot of the conversation around its UI was along the lines of "But I like it without all the wasteful whitespace" contrasted with "The whitespace at least needs to be consistent and the widgets need to look like they weren't thrown from the far side of a barn"?
Good design of the packaging has nothing to do with underlying OS, unless say it overheats a lot. TBH, the N900 had a fair design, I've used one, not talking from a bystander view, and it was good indeed. Save for the keyboard that perhaps costs 30% the device in order to be where it was (sliding and all). But also, the Nokia Nx's were slow as hell compared to iOS.
> The underlying OS makes no difference.
perhaps you've never experienced the bliss after setting up a BSD that just works 10 years after... and have never experienced the incredibly stable and snappy multiprocessing this miracle of a kernel (and OS) exhibits for decades now.
Let me tell you something - 20 years ago Linux was slow and unstasble as shit, and even slower on embedded. On the other hand FreeBSD and other BSD-derivates were super stable, but took more effort to setup and work with. They did not have the UI though, what Apple did was to wire their half-baked NeXT-inherited GUI on top of it and it flied.
I'm not even going to comment on the abomination called ObjectiveC, but matter of fact - the underlying OS workings were done in a brilliant way, WHICH, more than everything else enabled all the glitter tossed over the UI that you guys love so much. Like, there's a reason for game engines being written in C++ and not Python, right? Still a programming language though...
Sure lot of people adore what Sir Jony Ive did to the overall look and packaging of these products, and for a reason. But what truly distinguishes all these Mac products is what they can get out the hardware.
Sorry, but win3.11 did not work well on a 128kb RAM device. I've followed everything MS released since DOS 3.30 and witnessed firsthand the evolution of Linux and many of the distros. Nothing comes close to what Apple could do and is still doing with their hardware/software. No matter if you like Tim Cook (me personally - not) or Steve Jobs (very inspiring guy).
One of the reasons MacOS could draw attention from developers, who now form very important part of the user-base, is the fact they have a Unix-like thing at their disposal, and a very fast unix-like thing with some sort of a not-so-disgusting UI (wait for MacOS 26 though).
Nobody cares about darn window shadows, edges, or the unreasonable animation effects that we'd be turning off sooner or later.
Nokia was already fucked because it had set up a system in which internal divisions designed competing phones, as a result it had flooded the market with similar but-not-quite-the-same handsets with overlapping features, and it had missed out on usability advances that iOS had made.
Symbian was undergoing an overhaul which would eventually lead it to be ’good’ again, but by then it was too late as Android and iOS were already eating its lunch. And around the time of the N9 launch (touchscreen-only Maemo/meego phone), Stephen Elop took the helm and issued the famous “burning platforms” memo which put Nokia on the path to windows phone exclusivity, purely to the benefit of Microsoft, who delivered the killing blow by first forcing the doomed “Windows Phone” onto them, then buying the mobile phone division so MS could churn out more doomed handsets for their stillborn mobile platform.
tl;dr - The company was a clusterfuck riding on name recognition and then an MS plant killed it.
Linux on the N900 was neither here nor there. It was a skunkwork effectively, a niche device for nerds (and a great one). But it neither sank the company nor could have saved it.
The N9 could have saved the company in my opinion. It was great. I had it for some years before it broke and then found the Android I had afterwards to be poor compared to it.
A bigger mistake was to not give the N770, N800, etc. phone capabilities. I was buying a new phone around that time, and thought those devices looked cool; but I couldn't even consider them, because they couldn't do basic calls or SMS. They fixed that with the N900, but had lost their head-start.
perhaps because phone capabilities require more chips, and SDR that would've made the N800/N900 too pricey. but, honestly, this thing was slow as shit, I loved the design so much, and hated this half-baked Debian equally.
The fact you could run apt on it did not help that much for the regular user.
There's been times in the past when I've had nontechnical stakeholders present for otherwise technical meetings. A little bit of colour and a little bit of animation can go a long way to helping people who may be less familiar with this type of diagram to understand it better.
All the better if I can take an existing diagram and just spruce it up slightly for presentation.
I’ve done my fair share of diagramming and one thing I know for sure is markup (In he visual one) needs to be as clear as possible.
As someone who started with demo scene and all I can understand the drive to have moving parts and all the gay stuff, but many people get easily confused by colours and animation.
I have experienced the decline in interest in Perl firsthand - having teached a class in Practical Perl Programming for 10 years at a local major university. First years saw 270ppl, second 150, then 100, 80, 50, and I think the last issue was 12 people.
I can speculate a lot about what killed Perl, or at least what called the schism, and in general what was the cause of the schism had roots in what Perl failed to innovate on. The cultural stuff was a side-effect of it.
But then also - Perl has huuuge impact on so many other languages, including JavaScript, that its place in the hall of fame cannot ever be disputed.
Of course we should! And everyone who says otherwise must be delusional or sort of a gaslighter, as this whole "innovation" (or remix (or comopression)) is enabled by the creative value of the source product. Given AI companies never ever respected this copyright, we should give them similar treatment.
likewise, nations may have to legalize in order to regulate the contents of whatever-white-powder users may stumble upon on the street. and let us be honest - no bombs can stop the Fentanil (or rat poison for all I care) from being mixed in.
reply