skysight-inc/HackerNews huggingface dataset:
> I have to wonder if seeing SV startups go to multi-billion dollar companies on a regular basis, has given CEOs in other industries a case of envy.

If so, they're learning the wrong lessons. SV unicorns become valuable because of explosive growth, not because they underpay their engineers. Just the opposite; a lot of engineers at SV startups are paid quite handsomely (especially the early ones at successful unicorns). SV startups don't win on cost-cutting.
FWIW, I have given major conference talks years back on my linux laptop with PowerPoint running via Crossover Office (wine), mostly due to my advisor's insistence on using PowerPoint. So that has already been a thing for a long while.
I do think there's the factor of the type of camera used: it's mentioned that it takes a while to take the picture.
I worked at a Fortune 10 in the early 2010s for several years. We had a small army of local and offshore Indian contractors through Larsen and Toubro Infotech, an Indian IT company. They were paid between $10-20 an hour, many couldn’t understand English. These guys have no CS background and would get stumped writing fizz buzz. But hey, management got ball game tickets and other favors from the L&TI reps. One of the directors admitted to getting a cut under the table after he left to go work for a competitor.

To be clear, we paid $120-150 per developer and L&TI paid them nothing. You’d see .NET code with a single class that has a few thousand lines of code, no concept of unit tests, integration tests, manual or automated acceptance tests, usability tests, etc.

Shelf life of most of this garbage was a few months if something ever did get delivered. This went on for years.

The whole industry is corrupt.
The only thing I have found that seems to go anywhere is focus on the work, not the person.

Give actual feedback on the actual project, not on her feelings, her confidence or whatever.

When I get frustrated and start expressing my feelings on HN, I routinely get sympathetic, emotionally supportive noises of the "atta girl" sort. What I need is actual engagement and that's much, much, much harder to come by.

Feelings come from somewhere. If I got what I actually needed, I wouldn't be having a hissy.

Is that at all clear?
The engineers may not have realized they were relying on one sensor, or they might be the $9/hour variety with no avionics experience who don't know any better.

The main problem was higher up. The overall design was bad, and Boeing didn't seem to have a handle on it.
Someone who uses MacOS might think Docker implies a VM perhaps? (Linux VM needed to get Linux Containers to run).
Why worry about meddling of elections by Russians when large American companies that make life/death products and one of the pillars of US economy goes around doing stuff like this, effectively committing a corporate seppuku.

I used to watch PR videos from Boeing on new planes being tested and feeling sense of wonder and awe. Now I feel like puking.
Of course not the rank and file. But the ones in corner offices.
This is a really important moment in your life. You're on the right track asking questions about it. I do have some actionable steps you can take.

1.
Please, please read the book "The Five Love Languages". Don't say another word to her until you have this short book in your head. It will explain, right away, the things you need from your wife to feel loved and happy with her. You have noticed resentment building in you (its good that you're self aware and willing to talk about it). Being resentful can lead to you being really aggressive in an argument which will drive her even more into personal goals and then your marriage is over. Remember, she is still the one you fell in love with. Right now, she is high on success.

2.
When a person is selfish, it is extremely hard to take away the euphoria they are feeling. For the purposes of this online discussion, it maybe you who are selfish. However, because you're the one asking about it, know that you will be the one to start the both of you down the right path. You will be the one who understands what is really going on. That is a big job, and you'll have to commit yourself to making the marriage last and work in a better way.

3.
People are selfish. You, your wife, your children, the guy who cut you off in traffic ... the people at work who think your wife is amazing your husband just doesn't understand you. She won't listen to them, unless its been your tenth argument and you yelled at her again and have not met her love language.

4.
You can be totally happy with your wife. She can totally respect you. You'll need to use forgiveness and an ongoing understanding about how great marriages work. You learn about software techniques all the time, you're on HN after all! So now, spend a few moments learning about great marriages and how they work from the book, "The Five Love Languages".

5.
Imagine, try to really imagine this, that your wife is unfulfilled as a person and as a wife. She does not have bad intentions. She is emotionally starving for something missing in her life. What if you could do, say, or in a small way meet that emotional need? Would you be willing to do it? If you're not, then someone or something else will!
Right here, I suppose.
> What we really need is approval voting / range voting.

What we really need is for everyone to vote.

Or, for nobody to vote, which would trigger chaos. As Mel Brooks said, "Out of chaos, comes order."
Having been someone who's had to "setup" the db, app, etc. before ORMs were mainstream, you're wildly overestimating how complicated it was. It doesn't actually take very long, you'd maybe save a couple of days or so on a month project, having to write a a CREATE TABLE and then the corresponding class are actually trivial. You make the design decisions when you write the create statement, the class is simply a copy of it.

It's just a bit easier, not a lot. I certainly use ORMs now, but it's a convenience rather than a revolution. The truly revolutionary thing for code from that era of C# were lambda expressions.

In all honesty, he's an idiot for not updating his skills. If he simply learnt a bit of modern EF and learnt how to use git, he'd run rings around you. I'd note that "proper" source control practice has been around for well over a decade now (SVN was adequate, just not great for distributed teams), so he must be really adverse to change.

The unit testing and DI, on the other hand, is all pretty useless noise in a statically typed language like C#, for all MS push it. The only benefit in DI is keeping the same instance of the EF around, and it's pretty hard to actually get that working properly through-out the entire stack when you want to do anything even remotely creative.

As for unit testing, never seen the benefit. I took over a project with something like 50% unit test coverage that I never bothered to keep up, in 3 years the existing tests caught 1 bug.

All that highlighted to me that it was an utter waste of time and money it was writing all those tests.
Titan has smog in the visible spectrum. Details matter! The technology is also not that mature, yet.
Having a good shell (like zsh) that shows available flags with descriptions when hitting tab goes a long way toward not having to remember tools' flags.
This Android phone tells me proactively if it notices an application using lots of battery life or network bandwidth. And if I'm inquisitive it will let me see how much they used anyway when it didn't alert.

For example apparently Chrome used 3% of the battery life so far today whereas a game I was just playing already consumed 5%
> There are still some I/O issues that the team is actively working on, but early benchmarks are quite promising.

=/

Hoping to run my R code on WSL 2. Glad I got the answer. I wish you guys well on I/O issues.

Is there any performance hit for WSL2 in regard to process forking? I recall that how window and unix deal with process is different (my R code uses mclapply parallel package for unix). I'm curious if there will be any performance hit that stands out versus running on a unix system for parallel/concurrency code.
I believe you can actually compute the sunrise time of a location/day that doesn't have a sunrise, and it would be just a complex number (root of some analytic function).
https://sci-hub.se/10.1126/science.aaw9486
RenderDoc offers more useful features than the Metal debugger too. For example, RenderDoc is scriptable.
Newsweek: the ones that won't quote 'concentration camp' when bashing the US, but will gladly so when talking about China:

https://www.newsweek.com/xinjiang-uyghur-crisis-muslim-china...

No, thanks.
Seriously, is this a threat or is it the unexpected boon of getting a jump-start on terraforming? If you could press a button and "contaminate" Mars with life that would start spreading and generating an oxygen atmosphere, wouldn't you?
Part 2 - https://developer.ibm.com/tutorials/l-awk2/

Part 3 - https://developer.ibm.com/tutorials/l-awk3/
Why has this article been flagged?

I take it this flag is down to users flagging it as an issue. But isn't that exactly the point the article was raising?
It depends on accent, and short vowels tend to be pure in all accents of English, to the extent they are in other languages. Long vowels can become diphthongs though. Here are the vowels in Received Pronunciation and General American (and one other accent): https://en.wikipedia.org/wiki/Lexical_set

Even RP has some pure long vowels (e.g. NURSE, THOUGHT, BATH).
FLEECE and GOOSE do tend to be realized as narrow diphthongs, though.

In my own accent (Scottish), except for the four diphthongs (PRICE, PRIZE, CHOICE, and MOUTH) of which the first two are allophones, all the other vowels are pure. I verified this while developing a formant speech synthesizer.
Even the NVIDIA drivers on Linux are superior to macOS' drivers. The problem with the NVIDIA drivers is that they don't play well with the rest of the ecosystem, but they do work. The only area where Linux is behind in graphics is on mobile, where the GPU vendors are perpetually unable to write working drivers.

I'm a professional graphics developer and I prefer the tooling on Linux to that of macOS.
Might be some stupid questions, but maybe someone can enlighten me:

Could this explain the Schrödingers cat experiment, i.e. the light moving through both of the two slits? If light has a self torque, a single beam of light could travel through both slits (almost) simultaneously depending on the torque.
Also, can someone clarify whether every beam of light has self-torque? Or do you need to create a beam of light in a special way to achieve this property? If every beam of light has that property, wouldn't that mean that light doesn't travel in wave form, but rather in a wave-cylindrical form?
Many years ago, I used X for remoting in to a variety of systems continuously all day, every day.

Two sort of non-obvious humble things have eliminated my need for X:

- ssh

- emacs + tramp

and there's always been VNC, but all I actually ever used that for was to get to PCs anyway.
I think the big problem is that there is no water on Venus though?
Even at my current job in a startup, 90% of the code I own can be considered legacy.

The startup is 7 yo, I joined almost 2 years ago.

The gap between old and new features is enormous .. and it will take years to reach some cohesion.
>In my mental model of this kind of development (which could be wrong), you'd absolutely not want the 10x hotshot coder, you'd want predictable worker bees to faithfully transcribe from one specification format to another specification format slightly closer to the metal (or to a verification tool) until you eventually have a product that is working as designed.

Which gets you exactly what happened here. The 10x "hotshot coder" isn't a coder who vomits out 10x more code than another, but the coder that knows the right code for the job and also understands the provenance of from whence the data operated on comes from, and to whence it goes.

Software engineering and computer science is about so much more than coding. It's about knowing the types of problems an implementation can solve, what boundary conditions have to be taken into account, and knowing what code isn't the right code. All for any subject matter area they end up operating in.

You'll be amazed the speed ups you get from not having to write ten different versions of code implementing the same functionality before finding the one that plays well and reads well with the rest of the system. All that extra time spent not coding can be spent going over the operating environment to make sure the specification you were handed is actually complete.

Unfortunately, I have the feeling Boeing would have hidden that information regardless seeing as their design doesn't even necessarily comply with 25.173 as written without interpreting it as allowing a computer to magically make an unairworthy frame airworthy. But that is beside the point.

Once your management starts assuming the process will spit out product as high quality without your expertise, you can pretty much set up a timer to measure the time until the first impedance mismatch from a false assumption not rooted out rears its ugly head.
At the minimum, to be considered active: you need to submit a weekly update about your progress every week (probably 5-15 minutes max).

Every week we release about an 1 hour of video content for you to watch.

Every week, there are group sessions with other SUS founders for you to talk about your startup. These should be about 30-60 minutes.

We provide discussion questions before your group sessions to give you topics to think about. Between 10-30 minutes of prep depending on how seriously you take it.

If you come to a SUS meetup in person, those are probably 2 hour events.

As you can see, it's probably a max of 2-3 hours a week in regards to time we ask of you. How much time you dedicate to your startup is up to you.
The pure geek in me really wishes they'd bring back SFU. Windows has a really impressive mechanism for implementing subsystems (I can't remember for sure, but I believe win32 is actually implemented on top of this layer).

I'm sure there's far more complexity involved than I could imagine, but I've always loved the idea of having a bunch of different subsystems running without the need for virtualization.
That's pretty typical. "I don't need it, so therefore nobody should need it, so therefore I will remove it".

Unix is different things to different people and to remove the network capability from X is a step back, not a step forward. There are a whole pile of neat things that you can do with networked graphics, so much, in fact that Plan 9, in many ways a successor of Unix used that theme as the core of many of the system services. All of them work locally as well as remote.
Basic cooking taking a lot of time is a myth. Sure, if you don't have a kitchen and a fridge at all, that is a problem.

And I suppose if you don't know how to turn on the oven then the whole endeavor looks like marathon running (and winning) looks to a bed-ridden person. But your goal is not to be a professional chief in 5 star restaurant, it is to cook some soup from whatever is in the fridge, boil some pasta, fry some eggs and chop up some greens. Cook enough to last a week and you are set.

Ask your first generation immigrant coworker to teach you what they cook (or ask them to introduce you to their parents :)).
Microsoft first licensed Internet Explorer in 1994. It's most used engine Trident was released in 1997. IE/Edge was discontinued in 2019. That's one hell of an "Embrace Extend Extingush" cycle.
I hear you. It almost always is what people meant but most of us (myself included) rarely think about the distinction.
How Much Phone Storage Do You Need?
Correct me if I’m wrong, but terraforming Venus’s atmosphere wouldn’t do anything about the pressure, right? Even if all that CO2 became oxygen, and it cooled off a bit, Venus would still have almost 100 atmospheres of pressure at the surface and still be basically uninhabitable.
It was open sourced because it was a cool piece of technology and it would have been a shame to keep it back, but it is no longer in use at Workiva.

Source: I work there, although I have literally nothing to do with this project.
This would, for instance remove the possibility to run an interactive program on a CUDA server mounted in a rack in the server room while displaying the results on a workstation without the likes of 'VNC' to screw up your display and/or huge latency.
That's the two-slit interference experiment. Schrodinger's Cat is completely different.

And no, this has nothing to do with the double slit experiment.

And no, not every beam of light has self-torque. You need to create it in a special way.
This year, each lecture is no more than 20 minutes. On any given week, there will be a max of 1 hour of video content for you to watch. More important than the lectures will be dedicating 30-60 minutes each week to participate in group sessions with other SUS founders.
I guess I might have.

I was arguing that only NeXT and SGI had a graphics workstation culture, where having UNIX underneath was more of a detail than anything else.

No one cared that much of writing POSIX daemon and CLI tooling, the whole point was making the best use of the GUI frameworks, IDEs and their GPUs.

Even when SGI offered IrisGL as the basis for OpenGL, they kept the best parts for them.
Could you please link to any good self-contained material that covers the info on this advantage, for a layman like me? This sounds like a massive opportunity space.
Not true. Copy-pasting from my Ryzen terminal:

$ spectre-meltdown-checker | grep "NOT VULNERABLE" | wc -l
12
What can Wikipedia tell us about human interaction?
DST. Some countries (Brazil) switch over at midnight instead of 2:00 am. One day of the year has no midnight.
You might have a system where neither side can force anything down the other side's throat. To do that, you might need something like one legislature where the cities predominate, and another where the rural has more sway. You might call it a "bicameral legislature" or something.
This Week in Programming: Awash in the Waves of the Tech Conference Glory
Higher pay grades equal higher responsibilities. Accountability for an incident cannot ever sit with a single individual in an organization, nor should it sit with no individuals. Why was this allowed to occur? What processes failed? If it’s an endemic issue, getting rid of employees at the bottom won’t prevent future issues and potentially future loss of life.
An easier way to understand this whole climate debate as 'a rise in temperature means there is more energy available in the atmosphere'. That energy can have many effects. It can cause local heating, but it can also move large airmasses around and if those airmasses are colder than the normal for that region the movement will cause a huge swing in temperature.

This is one of the main reasons the average 2.5 degree celsius change (which on an absolute scale would not make a huge difference in the first place, most people would hardly notice) is such a huge affair.

It can cause local variations that are a very large multiple of the 2.5 degrees, much like a heatpump does not require a whole lot of energy to move a much larger amount of energy around.
> Most people won't support your opinion - because they are paid trolls (a large fraction of app posts, because a comparatively small - 'only' hundreds of thousands - trolls post in insane quantities) and because many online spaces are shaped by trolls and by people who are too afraid of expressing their opinion freely.

I wonder if that situation is exclusively true in China, or if similar situations exist where it is covert, rather than overt.
It would mean you have a much harder time finding out if Mars once had life, if instead you're detecting mold that hitched a ride with your spacecraft.
Yes, it’s a gateway drug, like firefox and libreoffice.
I have large legs (around) from all the skating growing up. Don't have a defined 8 pack, never really had a strong core, it's mostly legs.
I wouldn't be so cynical. As with all things, tech comes and goes in cycles. I think with the limit to Moore's law rapidly approaching for current silicon, there's a good chance that efficiency & simplicity will become front and centre again at some point.

Not sure if this will mean new architectures, operating systems & better tools.. but one can dream!
As an aside, which laptop do people here prefer for windows dev? I am split between Surface laptop and Lenovo X1 Carbon.
Because of the thickness of the atmosphere, Venus is probably more suited to floating cloud cities.
The thing is, you don't need explicit support in the display server for remote. RDP works just fine on Windows, yes even single-window forwarding, without it.
I already use WSL1 as my main setup for web dev at work. If Windows comes to a point where doing anything doesn't immediately make the fan spin to maximum RPM, I'll be very happy to call Windows my digital home.
What you just said is such a realistic analysis and terrifying....I will keep on running linux on bare metal hardware no matter what. I like to know what is ACTUALLY happening inside an OS,not being told by a company what is SUPPOSEDLY happening.
Probably not. We don’t know how that would affect other planets in our solar system. Besides you would need another button for “water”. Without it no multicell organism is capable of growing.
This post is literally a link to the source code published on Github, and the commits aren't obfuscated either.
They should be jailed for self reporting the cover up of other employees?

Because that's what you're suggesting, and it sounds patently ridiculous.
That's because it was as much a power play as it was a technical effort.
That's a simple question with a complex answer. The answer is 'it depends'. Yes, there definitely are cases where execs should be jailed for their employees crimes, and others where that definitely should not be the case.

For instance, if an employee of a company embezzles a bunch of money from either a customer or the company itself then the execs should typically not be culpable. But, if the execs themselves were the ones that ordered the employee to do this, either directly or through the 'nudge, nudge, wink, wink' method of communications (and there is corroborating evidence that this indeed happened, for instance the issues not being limited to single employees but being institutionalized) then yes, they should definitely be punished as though they themselves were the ones doing it.

It should not be possible for executives to use employees as a cut-out layer when crimes are committed.
None of the freedom and plenty of tracking while you do just about anything on Windows.
Thankfully, at least in this case, the same is not true for companies. When the highest level of leadership changes, its quite likely that the company, itself, will change as well.

With competent leadership, Microsoft has found a new business model which is working well for them without trying to control the direction of the entire industry. We've got other big players, now, that are far more concerning to me.
dell xps 15 with 4k display
Strangely that was not clear to me when I first started using arch. Probably because when I got to setting up networking it gave me the choice of the systemd way, or a variety of other ways.

But looking at it in relation to init systems it clearly says systemd was chosen.

That said, arch still lets you make decisions, unlike most distributions, where you become a consumer of other people's decisions.
The SV devs helped Chrome reach where it is.
credit to /u/gwern
RDP is a very weak implementation of what X is capable of functionality wise.