HN user

tanr54ok

42 karma
Posts0
Comments23
View on HN
No posts found.

Well I didn’t say multiple screens didn't serve a purpose, did I?

Having said that, is there any good evidence of a fair comparison of dual screen vs a fast switching single screen. Most Mac and Windows setups make switching so tedious and slow it’s pretty obvious that dual would be more productive.

I would not be surprised that a truly friction minimized single screen setup (total switching latency from input to display <100ms... which is technically easily achievable (and done in many special purpose devices... just not in PC software).. and ergonomic switching key would approach dual screen in productivity. I mean, this is the typical setup I and many others use on a Linux laptop for dev work. By the time someone gets MC on OS X up, I can literally switch “screens” 3 or 4 times.

I enjoy a multimonitor (4) setup, but I’m not about to trade off battery life and space for it on the road.

Frankly it’s just easier and cheaper to buy a second monitor with state of the art, for most people. I get that. I use OSX and Windows too.

Also, I would expect more than 2 monitors to increase the gap.

So what? What’s missing is that unless something depends on the ordering of those ids, it really isn’t a race condition. Just plain happening of events is the inevitable passage of time, not a race condition. What is interesting about what happens downstream with those IDs?

You’re not wrong that not all race conditions are harmful, but i feel you’re doing a pretty bad job of explaining what a race condition is.

1) False. Software screen switching is easily instantaneous. If you literally have two front buffers which, you must for a dual screen setup... there’s no reason you couldn’t flip between them at the refresh rate of your monitor (which is ridiculous but doable). Workspace switchers that run on shitty old X can be and many are effectively instantaneous. Not sure about Windows, but I assume something exists.

There’s more to life than Mac OS X.

3) you can still have a spatial layout of workspaces even with one viewport.

I’m not saying you’re wrong. But winedb gives garbage status to the latest, the installer on playonlinux is unverified and posted by a banned account. I have found no testimonial that the latest works now other than yours.

So here’s the thing. Even if you’re right (and not confusing some older version as the latest.. that often happens in these discussions... what do you think is the latest version of adobe CC?), this is a terrible support story and not something that most pros that rely on adobe tools want to mess around with.

One of the winedb reviews says this:

“adjusting parameters in some effects such as lens blur makes program unusable (must kill app)”

Wonderful.

The crowd on HN is biased towards software development, something overwhelmingly well supported on Linux (it’s my daily driver as much as possible for that). But I assume there is a long tail of other professionals here... using their systems for actual industry work that isn’t programming. An area that is terrible on Linux sadly.

Photoshop and Illustrator and Premiere are not “defaults” on any system I know of. If you need to draw an arrow on a screenshot, there are ironically more free beer and open source programs available on Windows to do this (even gimp). If someone wants to pirate adobe that isn’t an aspiring designer (which is sort of a rite of passage), and has it just to collect that’s cool, but irrelevant... but I assume if someone has the CS on their machine it’s to do actual work with industry standard tools - that certainly is the case for me.

There are plenty of things to do in Excel that are best served by excel and not crunching market data. I have tried libreoffice calc multiple times in the past. Google sheets is also cool for certain things, but no excel killer.

And here’s the kicker: If you need to just put arrows on screenshots or an app with text in cells (and you’re not a dev), then you don’t need a desktop running Linux or windows... you can do with an iPad.

He mentions the mech was changed in 2011, mentions there’s a probably little used retrofit and at the end of the video he comments that there are likely many compromised ones still out there.

Which is pretty expected if you've seen how buildings are maintained in general. I haven’t encountered a lock that doesn’t have this vulnerability in any 20th century post-war nyc building.

Just because information is out there and accessible doesn’t mean it has much mainstream penetration. Locks are a very niche hobby. Most of my friends and family don’t know shit about locks any more than 30 years ago even though the technology is clearly documented and explained on YouTube.

YouTube has made pretty much everything widely accessible. Doesn’t necessarily change the market.

Who picks a lock to break in? Common thieves have no need to pick locks.. totally dumb for a couple reasons.

Contrary to popular nerd belief... door locks in the US are not that easy to pick. Many have anti pick features like reverse sidebars that while not impenetrable increase time or skill required. While the lockpickinglawyer has videos, note that he is extremely skilled with tons of practice, it still can take more time than breaking, and those aren’t field conditions. Just break the door in... stealing might as well use forcible entry.

Where picking is useful is covert spying, and if that is your threat model the addition of the second or third lock doesn’t really mean much.

Also, if you are a doctor and your primary motivation is helping people, wouldn't you want to help many people with simple problems, than few people with highly complex problems (which most likely have a higher risk of failure)?

Your analysis completely falls flat here. Not all doctors are motivated by the same things and yet most of them would consider their primary motivation helping people.

Neurosurgeons are a prime example. They would very much prefer few complex cases (not everyone gets a brain tumor thankfully) as their way to maximize benefit rather than manage cholesterol meds for 100s.

Speciality surgeons by their nature are motivated by a certain degree of risk.

The incentive for doing difficult procedures is often because they are challenging. Compensation for doctors in the US isn’t fully correlated with difficulty either... with no offense to my dermatology colleagues making more than most general surgery sub specialists.

The second half of your post is survivor bias.

The first part of your post is pure hyperbole. There are plenty of places less crime ridden then Baltimore or Detroit where you absolutely have to lock your things or they are likely to get stolen. Pretty much any urban area in the US. Most suburbs as well if you park on the street. Kids will go down and just try doors. They have no intent of picking anything or forcible entry, just snatching the low hanging fruit.

I have lived in northwestern Nebraska so I get it, there are places where you don’t have to ever lock your door.. that is the exception.

To counter your friend: I lived in one of the lowest crime rate suburbs in the US. Stupidly left my door unlocked in an apartment parking lot overnight.. everything of value was cleaned out in the morning.

I’m curious with something as poorly understood as takotsubo, how they are so confident to rush to the conclusion that the wasabi must have triggered. I actually read the full text and I dont see any discussion on eliminating confounders, and this is just one case.

At best this suggests further research is in order, but I’m not convinced anything can be definitively concluded here about the cardiotoxicity of wasabi.

Case report or not, what passes for medical research makes me shake my head.

Your post manages to say nothing correct. Javascript did not invent callbacks, asynchronous programming, or event driven programming. Nodejs popularized it in the 2010s but you are claiming credit for something that has been in common use since the 70s. I have no clue how anyone can speak with such authority while clearly having not done a cursory glance at programming APIs available in the 80s and 90s.

Lighttpd was released before nginx and was wildly popular for a good while. Not to mention other servers like AOLserver in the 90s.

The use of non blocking sockets was nothing new, used heavily in C code throughout the 90s and is the basis of asynchronous processing (refer to Stevens Unix network programming). You should also read documents by John Ousterhout written in the 90s about this topic.

Now just about every major GUI library was targeted in C or Pascal and used an event driven callback model. You can refer to the Windows API, the modern Mac carbon API which was developed in the 80s at Next and the older Mac SDK. The Windows SDK allows event driven programming for UI and IO. tcl/tk. Just about anything on top of X (ie Motif, GTK). The list will go on and on.

Do some research before making bold claims about C programmers not understanding asynchronous programming and callbacks.

Also I think the other reply is correct in asserting that your definition of async is making distinctions without differences.

Eg from 1995: https://web.stanford.edu/~ouster/cgi-bin/papers/threads.pdf Note that event driven programming was nothing new in 1995.. it was the basis for the Windows api designed years prior after all, but this was around the time that multithreading was pushed for everything.

Heck fibers: https://docs.microsoft.com/en-us/windows/win32/procthread/fi... have existed in the Windows api since at least 95.

I am aware of that. The “get off my lawn” is a reference to the fact that those of us who are older would not have had access to such modern conveniences as flash memory in high school, and that the poster is too young to be aware of TI calculators that didn’t have this feature.

Anyway I used an HP48GX throughout high school (carrying a TI83 only if absolutely necessary). The HP had a pretty much universal following in France.

As an example, I met a fashionable young Chinese lady with an apparently large income who was traveling the world

Change Chinese to American, or Ethiopian in that part of your comment. This is selection bias pretty hard.