Hacker News new | past | comments | ask | show | jobs | submit | jmb99's comments login

But that's missing the point. You can be doing all of those things but your manager still may not like you. Admittedly they're probably more likely to like you if you're a good employee, but if they like you and you're a subpar employee you're going to be much better off than if they don't like you. And, if you're a stellar employee, you'll likely be presented with more opportunities/more favourable tasks/etc than a stellar employee your manager doesn't like.

You can take the view of "I'm doing my job" but don't be surprised if those around you who are more liked by management get picked up for promotions/etc more than you. Most people (management included) are not 100% objective in their decision making, and someone liking you (or not) is going to influence their decisions involving you.


I personally measured over 90dB in a friend’s apartment downtown. NIOSH recommends exposure to levels above 90dB for less than 30 minutes per (work) day. She said it was that loud 24/7, and I believe that.

If you have some evidence that it’s safe to listen to sound levels above 90dB for extended periods of time, I’d recommend you publish it.


That's not what I asked. I am asking whether there is even any serious claim (as opposed to your simple assertion) that someone's hearing was damaged.

Again, I'm not going to go searching the internet. Engaging in these comments is already more work than is worth it. I'm never going to convince convoy supporters they are wrong.

A woman took legal action against the protestors. In her action she called on an ENT. The ENT make the statements I outlined above under oath.

Search for it if you actually care. Again, I'm not wasting my time because nothing is ever good enough for the people who align ideologically with the convoy. The dismissiveness, what aboutisms, and misdirection that follow are never worth the effort.


Again, I'm not going to go searching the internet.

Yet you imply that others should do exactly that in order to take seriously your insinuation that actual bodily harm was incurred. If you have proof that someone was physically damaged by the blowing of the truck horns then it will a simple thing for you supply this information of which you have implied you are the possessor.

If you do not have it and have never had it then you could also help by just stating that, so that no one wastes their time.


I would argue that >90dB measured inside apartments for weeks on end 24/7 isn’t peaceful.

Unless I missed a memo, Linux LTS is 2 years of support these days. Many distributions offer 10 year LTS releases, but I’m not sure of any off the top of my head that currently offer more.


My point was more so that you can upgrade 20 year old devices to Linux 6.X! You're correct though.


I feel like a couple things were mixed that aren't the same. The commenter upthread said 10 years for Windows OS versions. I took that to mean e.g. "Windows 11 will be supported for 10 years from initial release".

Sure, you can often install a modern Linux distro on a 20-year-old device (though just as often, you cannot), but that's not the same thing as a single version of Windows being supported for 10 years. The analogous situation is indeed LTS versions of Linux distros, which certainly don't have 10-year support lifetimes, let alone 20.

But the support lifetimes make sense for the various vendors. Apple doesn't need to support a particular major version of macOS or iOS for all that long, because they make sure new versions of their OSes will run on fairly old devices (all of which are devices they've built, and have full control over), and they aggressively push people to upgrade to new major versions as they come out.

Microsoft has a lot of customers who value stability and consistency above all else, and on top of that, they have to support a wide variety of hardware that they don't and can't control. Supporting a major version of Windows for many years makes sense for them.

As for Linux, there's no one single source, so a rolling-release distro can decide to only support the bleeding edge, whereas a cloud provider might roll their own distro for server use and decide to support that for a decade, if they think that's what their customers want.


Coverity will definitely warn you about use-after-free. It’s not a “correctness” tool, it’s a static analyzer and probably the best one out there (imo). Yes in this use case it’s probably not too important to care about, but really any code base of importance should be run through it on a fairly regular basis.


Besides not being perfect, it requires full access to the whole source code.


Coverity can’t find all use after free bugs.


Unless I’m mistaken, Rhapsody (released 1997) used LF, not CR. At that point it was pretty clear Mac was moving towards Unix through NeXTSTEP, meaning every OS except windows would be using LF. Microsoft would’ve had around 6 years before the release of XP, and probably would’ve had time to start the transition with Win2K at the end of 1999.


Every OS except the one that had 95% market share in late 90s. Apple was only propped up “Weekend at Bernies” style to appease regulators.


brew install --cask xquartz

Or install from the project homepage [1]. Then just launch the X11 app. Note that it does require the application to be built for Mac - it’s not an emulator, just an implementation of the X11 APIs.

[1] https://www.xquartz.org/


This one is a bit more reasonable (to me at least). It seems to be an internet/texting convention that messages ending with a period are more formal/serious or potentially angry/irritated, whereas messages without a period are lighter/more fun. As an example:

“Have you taken the dog out?”

“Yes”

Vs

“Have you taken the dog out?”

“Yes.”

The second comes across as the responder being potentially irritated at the asker. I believe that this comes down to the amount of effort required to type the reply; adding a period is making the explicit choice to do so, whereas not doing so is the default. This isn’t the case for sentences in the middle of a multi-sentence answer, since a separator is needed anyways. But I find myself not adding a period even at the end of multi-sentence messages, and I automatically read any message ending with a period with a different tone than one which does not.

Maybe I’m just nuts though, that’s always an option. But with text being such a relatively limited medium for conveying emotion in short messages, I think this is a reasonable solution.


Not really sure how it could? It’s just effectively adding ~5” of wire and a differently shaped connector. Unless you’re worried about the fraction of a nanosecond the extra wire will add...


Unless said hacker has a big magnet.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: