skysight-inc/HackerNews huggingface dataset:
- Linux is more portable than BSD
- Linux is one of the standard server OS offered by providers, BSD isn't

that's the big one there. My favorite, Hetzner (not only mine, they have a ginormous amount of dedis) offers BSD but a) not all servers are compatible and for older servers you can't even know whether they are without booting into Linux first b) it's much more of a hassle like installing Linux gives you a ready-to-go system while the BSD install needs tweaking with sysctl and network both.
Dialogue in Jason Bourne movies has always been low. But in this movie, it's approaching zero. The new Star Trek movie, "Fast and Furious in Spaaaace!", is not exactly dialog heavy. That's new for that franchise. But there are other movies.

There's a new Harry Potter book out today. Kids were lining up at Barnes and Noble for it last evening. Words are doing just fine.
I used to run everything on FreeBSD. It's a great operating system and incredibly stable and I loved every minute of sysadminning a FreeBSD box. Honestly, what changed was Ubuntu. Being able to have a fairly robust server on the cheap and maintain it fairly well with just a few apt-get commands was a huge game changer.

Admittedly I haven't tried running FBSD since 4/5 timeframe and I'm sure quite a bit has changed since then, but I used to spend hours trying to patch and compile upgrades to software. The ports system that they used at the time (and might still use for all I know) was great for installing stuff, but if something didn't exist in ports or was a few version behind, you were compiling and installing from source.

aptitude has 99.99% of everything I've ever needed to install and manage and some of the newer package management systems like npm and the like cover everything else. What used to be hours each week of administration work has become minutes a month. It might be less secure, it might be slightly less robust, but overall I don't even think about systems administration anymore and (to me) that's such a huge savings in time that it's just not worth trying to go back.

And as emersonrsantos mentioned, I can almost guarantee that every hosting provider has Ubuntu in some form or another. If I need to move to a new host, I can have the system set up and be in business in probably less than an hour. What used to take a few full-time sysadmins has now been replaced by a handful of devops guys that not only manage the systems, but also help my engineers automate and improve our development workflow and pipelines. And, as he also mentioned, I can throw a rock and hit a Linux guy. Finding a FreeBSD expert is nearly impossible and they always cost a lot more.

But, it was my first unix and I've got a lot of love in my heart for the BSD way of doing things. (NetBSD and OpenBSD are other fond loves of mine). I ran a hosting company in the early 00s that was powered entirely by OpenBSD off cheap commodity hardware. And NetBSD runs on everything, which is also a pretty cool plus.

These days, I'm content knowing that my kickass Mac desktops owe their existence to the OS I grew up loving.
An analysis of word/n-grams/length in English subtitles vs movie run times would suffice, and I believe both are available, but probably not in a well structured format.

Flesh-Kincaid vs year of release in those subtitles would also be interesting...

/just planting seeds of ideas or there in hacker space because I'm too lazy to do it right now.
It's easier to find Linux admins and it's easier to look up Linux stack traces on SO. "Nobody ever got fired buying IBM," updated for the modern age.
Easy tool to generate backdoor
I understood you perfectly well. I was just pointing out one of the obvious mistakes.
Wow, that's pretty rough... Sorry to hear that.

I had a similar issue - I had to ask one our cofounders to resign and he was one of my best friends. (He started another company that raised conflicts of interest) It was very difficult. Here's what I took away:

1. Be honest with your reasons for leaving: If the fit is not there, it's not there - you can't force these things. It is in the long-term interest of the company to have people that believe in the vision. Anything less will only drag down morale.

2. Be grateful that you had the opportunity to work and learn with them: There's generally two ways to spin these things, "you wasted my time" or "this will be a cherished memory." It's always better to lean towards the latter.

3. Be resolute: If you're bent on leaving, know that this is the outcome walking out of that meeting. Startups are kind of like a band of brothers, it's easy to get guilted into a compromise.

An addendum to (3). Lack of communication is a common killer of startups, and it's usually built up over time, eventually leading to an ultimatum (like this). I'm not sure what the relationship between you guys are, but this can be a point of reflection / growth. If you have thoroughly thought this through, and there are no scenarios where you would be willing to stay, then that's fine. But more often then not, the points you bring up are invaluable to your peers - if they are receptive.

If it were me, I would bring up these concerns prior to your resignation and see what their reaction is. If you guys don't see eye to eye on these threats, then it's time move on.
I use OpenBSD for quite a few services, but end up using FreeBSD for my file servers (OpenZFS). If the progress on multiple CPU usage and virtualization continues on OpenBSD, the only real thing holding me back from getting rid of FreeBSD is the filesystem. I am looking at the progress of HAMMER2 on DragonFlyBSD to see if it is a good fit.
I also am constantly looking for better easier solutions for things like this. right now I think the wemos d1 mini is the sweet spot for ease of use/versatility.
These days mostly because of the network effect.

People both get more value from Linux and add more value to it by using it and writing software for it. Take docker or nix for example, huge value for Linux and not so much for systems, where they don't work or aren't first class citizens.
>> When the experimenter had their hands free and tapped the box with their forehead, the babies imitated the head action over 60% of the time.

There's an episode in Friends where Phoebe discovers she can change channels on the TV by blinking (if I recall correctly). Every time she blinks, the TV switches channel. Joey is there and he confirms it: whenever Phoebe blinks the TV changes channel. Every single time. Amazing. Then she loses it.

So, I'm not saying you have to be Phoebe to get in that situation, in fact you certainly don't. It's very hard to untangle the mess of causality when you're experimenting, especially if we're talking humans, even infants, who are incredibly, impossibly complex.

In any case all this is completely besides the point: it's impossible to know another person's mind state with accuracy unless you ask them and even then it's really hard to know for sure. So any experiment that purports to prove something about a person's mind state is most probably making a mistake, somewhere- same as papers purporting to show energy from the void and so on.
I commented it below too, but then I read your comment. I've found Hive is very enjoyable for a chess player (myself) since the strategy is different as the board is the pieces. If you want more level of skill, Terra Mystica was also very strategic balancing territory and resource control.
I always found peculiar of computer science in general the fact that once something has got good enough, people in the field feel the urge to throw everything out of the window and rebuild the whole thing, just a tiny bit differently, possibly making the same mistakes that have been done in the past.
...who are we to say you shouldn't be able to make your own choices.

Externalized costs complicate the libertarian approach.
Catan isn't bad as long as you're playing with players of the same skill as you.
When something like this happens: when the author of one of my favorite computer science text books releases an interactive notebook my main sensation is one of envy.

I really envy all the students who get to study Norvig like this.

Also, you'll probably have access to better health care.
Learning something new is great, but if you just want to turn the light on or off with a remote, you don't need a computer or the Internet:
https://www.amazon.com/dp/B0087EIDRS
True. That thing has more pins in less space than anything previously exposed to consumer handling.
Thanks for sharing your impressions; so much has been re-discovered / re-prioritized in computing over the decades!
I believe she's got a broader view.

"All the other milestones found her trailing behind her peers: potty-training, dressing herself, identifying colors."

These seem less like specific intellectual milestones than general developmental ones.

I think it's the integrated picture her daughter presents that she finds challenging, not solely her intellectual milestone schedule.
That seems a bit reductionist to me. Basically I think there are a lot of spots where a software developer provides say 500k a year of value to the company, and the company is looking to hire a person for about 150k a year in total comp. But if they hire somebody for 200k a year, it is not as if they are going to get rid of the person, it is still +EV for the company. And while the company might not be quite as delighted with the latter's value proposition, the employee is far better off negotiating aggressively and trying to "win". And as to why the company would not just try and wait and find a person for 150k, it is generally because good software developers are hard to find, and it is easier and lower risk to "overpay" a bit rather than lose out on a good hire.
Why large companies find it difficult to innovate
This is like saying that if somebody leaves their door unlocked, it's their fault if they get robbed and the robber shouldn't be held responsible.
The reason why this obvious option isn't part of the discussion is because thinness is just the smokescreen. The real reason Apple et. al. want to move towards digital connections for headphones is DRM. They want to control the entire signal chain of their valuable (Beats = $3b) music content.
I have vendors that require a certain OS. Often, its not even "Linux", its "Red Hat Enterprise version 6.x". If you've ever dealt with an Enterprise Software Vendor, you know the added level of fun of using something other than the strict requirements given. Red Hat is the new Windows for government vendors I've had to deal with.
Hmmm, you're right. I didn't find the correct US law.

A-ha! Found it! The bill which changed it was the Investigative Assistance for Violent Crimes Act of 2012, 28 USC 530C(b)(1)(M)(i), https://www.gpo.gov/fdsys/pkg/PLAW-112publ265/pdf/PLAW-112pu... and the law text is at https://www.law.cornell.edu/uscode/text/28/530C :

> For purposes of this subparagraph — (I) the term “mass killings” means 3 or more killings in a single incident; and (II) the term “place of public use” has the meaning given that term under section 2332f(e)(6) of title 18, United States Code.

It looks like Mother Jones is using the current federal definition.

Agreed, just because there is a definition doesn't mean it's a good definition. The idea that 18 people can be shot but only one killed should still make it be a mass shooting, but the FBI wouldn't count it. That's the argument given https://www.massshootingtracker.org/about , which uses a different definition to conclude there have been "1306 mass shootings since 1/1/2013"

Does feedback like this help you adjust your confidence levels? That is, might you think better of a Mother Jones analysis in the future, or give you less reason do the legwork?

While on the other hand, this op-ed piece appears to have undercounted the numbers, and for unspecified reasons uses "the traditional FBI definition" rather than the current FBI definition. (I, and perhaps you also, thought he was using that phrase to mean something like 'the current and long-held definition', not 'the older definition, which I prefer').

Does that make you less likely to trust the general argument?
Ports for building customized binary packages was a really nice solution to building a customized operating environment 10-15 years ago. It's still a good solution, but not so much better than what I get on Fedora or Ubuntu provide these days to justify letting devs and admins retrain themselves on FreeBSD during onboarding.
Great! Thanks very much.
I wouldn't be so blase. First, that was all true BEFORE Microsoft made Windows a marketing platform so all bets are off now. Also, that decision (what is safe and not safe) is not up to the regulated business to make, its up to the regulators. If you have not worked in a highly regulated business you can't know what this means in terms of arbitrary and unnecessary rulings and requirements imposed on a business, regardless of whether they make any sense. Moreover, for the first 10 years of its existence, HIPAA was a homeless step-child in the Federal government but fairly recently (5 years?) it found a enforcement home (and more importantly, a budget) in the Health and Human Services department. They are now building their budget and have developed their enforcement strategy that started with big insurance companies and large PPO/HMOs (you may have heard of some big cases in the news). HHS's plan is to ultimately push enforcement all the way down to the practice level.

FYI, most IT companies don't know this but back in 2012 or 2013 the new HIPAA enforcement division issued a decree that HIPAA applies directly to any IT companies that service organizations that handle personal health data. Prior to that proclamation I was operating under a signed declaration with my clients that my business was not responsible for HIPAA enforcement or violations (I just fixed the computers). That method of limiting my exposure and liability, according to my lawyer, was no longer feasible and I could be hit directly with HIPAA violations and fines and they required onerous documentation and procedures when dealing with PHI. At that point, at significant cut to my income, I dropped all my healthcare/medical clients.

In the long run the regulatory agencies are captured by the regulated business and the requirements imposed are fairly sensible but by my guess is that we are at least a decade away from that regarding HIPAA especially considering its only now starting to be enforced with audits and fines.
I find it funny that she mentions Gravity as an example of a film with little dialogue. My biggest complaint about the movie was that it had entirely too much dialogue. So much pointless, clichéd exposition about the characters, as if Bullock's needed any kind of emotional background. It really ruined the movie IMO.
It comes down to the fact that there are more people familiar with linux than BSD. Orders of magnitude more in the US. Unless you're working on something where the GPL is a concern, it's easier to default to linux.
Perhaps they have some security concerns. https://vez.mrsk.me/freebsd-defaults.txt - more admin time spent tweaking poor default security == more money being spent.
Absolutely true.

And because, as you say, "little of the Windows revenue come from upgrades," Microsoft didn't give up much income by making the Windows 10 upgrade free for one year (though it did add a bunch of server and bandwidth costs).

To compensate for falling PC sales, Microsoft is clearly heading online as rapidly as possible, with Office 365, CRM, Azure etc.

It's also heading cross-platform with online services and dozens of apps for iOS and Android, and Linux support in Azure and Windows 10.

Times change....

But my point was that the Windows 10 business model hasn't fundamentally changed, even if Microsoft manages to make a bit of extra money via Bing ads and Windows Store apps.
There's platform, and then there's drivers. There's no point on having an OS on a net-enabled device if that OS can't talk to the network hardware, for example.

Linux has had a ridiculous amount of work from a variety of sources in it's drivers. I once used a git animation tool (forget the name of it, sorry) on the linux kernel source, and the area where the drivers were put was buzzing like a beehive, as people from all sorts of companies were making sure their stuff was supported on linux.
It's pretty odd to see all of these energy-saving LED bulbs being made "smart", totally killing the energy savings.

(Not to mention the Rube Goldberginess of needlessly using wifi when you could use a few million fewer transistors on existing wiring.)
After 18 years of running FreeBSD on my servers, my $0.02:

Politics/marketing:

* Most "unix" admins only know linux and will advocate for it vigorously because it is so much better than.. "what do you use again? Fedora? Ah, FreeBSD, something with F, I knew it!"

* Management not always listens to reason but just wants a discussion go away, so they listen to the loudest advocates.

Knowledge/Community:

* It is easier to copy a solution to a linux problem from stack overflow than to read the FreeBSD handbook, understand the problem and fix it.

* FreeBSD only is fun when one has a higher level of expertise: Knowledge of sh and at least a basic understanding of make are required, being able to at least read c code makes life much easier.

* Reading docs is hard. FreeBSD forces one to understand the standard unix tools that come with it. That means one has to spend some time reading the docs (or at least skimming over them so one knows where to look when the need arises). If one does not understand the tools, even simple init scripts are black magic.

* No exposure to FreeBSD at all: most hosting companies won't even list FreeBSD as an option (though in most you'll find some unix geek who'll happily connect KVM or IPMI and insert the install-CD for you).

* The FreeBSD community is much less forgiving than the linux community: Ask a question that can be answered easily by reading the handbook or some man-page and the response will probably be silence (rarely flaming, just silence).

And finally also some points where one could argue that it makes sense not to use FreeBSD from an economic point of view:

* When using FreeBSD one is regularly forced to clean up linux-BS when venturing outside what /usr/ports provides: #!/bin/bash - or even worse #!/bin/sh that actually wants a bash - is one of the most common problems.

* When compiling software from source that does not come from /usr/ports one regularly has to do research what $leenox-distro-package XY provides because documentation just gives command lines for the most common linux distributions. "Soo.... what exactly does that software need to compile when the docs tell me to simply apt-get foo-23.5 and bar-42.666?"
Drawing lines is a stupid way of doing it, as:

1. With the mess of overlapping lines they've got, you'd suffer from severe overdraw (which is where raytracing really shines in terms of efficiency) as you can't efficiently cull lines (without clipping them)

2. You wouldn't get the ambient occlusion look where lines close to each other occlude / darken.

As someone who's previously compared Embree and OptiX (and we were given free hardware and support from Nvidia), Embree stacks up really well, and a dual Xeon can match a single top-of-the-line GPU fairly easily for pure ray-intersection performance.

Once you start putting complex shaders and layered materials on top, GPUs start to really suffer: there's a reason a lot of the GPU renders are mostly being used for clean renders like archvis / product design / car renders - they're simple to render. As soon as you stick dirt layers on top, their efficiency really starts to plummet.
So you are admitting that you are dishonest prick?
Small UAS Rule, Big Opportunities
Booklet Printing – Color Printing Company – ZX CHINA
I think what you might be asking is "what would more idiomatic XML look like?" And that's a fair question for people who haven't spent lots of time working with XML.

First off, I think attributes are evil. In theory, they're good, but nobody knows how to use them, so they shouldn't ever be part of your XML. They're simply elements with cardinality of 1.

The format would probably be better as:

<format>
<record>
<id>1</id>
<name>
abc
<comment>blah blah</comment>
</name>
<attribute>this is the attribute value</attribute>
</record>
<record>
...
</record>
</format>

This is a completely valid XML language, is much more clearer, less verbose, doesn't overload element names, doesn't abuse attributes, etc. etc.

One important thing that most people don't get about XML is that XML is a specification for describing data-interchange formats. XML isn't a format, or a language. The result of following the XML spec is an "XML format".

If somebody asks what format some data format is in, it's more appropriate to say "it's in an XML" rather than "it's in XML".
Many embedded Linux vendors don't release their code. They get away with it because many are only around for a short period and enforcement resources are limited.
That's not quite fair - some of the research into volumetric medium interaction and scattering is way ahead of the VFX / Gaming fields...
>> Actual write-up in Nature (which was linked to in the article):

Yeah, about that:

79% of them chose not to imitate here because their own hands were free, presumably concluding that the head action was the most rational.

Whether they re-enacted the head action or not, all infants who watched the adult perform under both conditions still used the hand action.

See what I mean? Who knows _why_ 79% of babies chose to imitate the researcher? The research assumes it was "because their own hands were free" - but isn't that what it's trying to prove in the first place? And where does that conclusion, about rationality, comes from? Certainly not something that the babies indicated, but rather the researchers' interpretation of the actions of the babies. This is... it's kind of like anthropomorphising animals. There's absolutely no reson to assume that babies where behaving rationally, or irrationally. They could just be moving completely at random, but the researchers go ahead and assign motives to them and "rationality" as well. What the hell!

And like the second paragraph says, all infants used their hands _anyway_. At that point it's obvious that the head action is just a random thing that some babies do anyway. Because if they know they can turn the light on with their hands, why would they use their heads _also_? If they don't know they can turn the light on with their hands, then how can they know they can turn it on with their heads? This just doesn't make any sense.
Or perhaps a return to discrete sound cards?
> Isn't that fact a huge tell-sign that perhaps you're not the kind of person for whom desktop Linux would be challenging?

Well, sure — but I didn't spring forth fully-formed from my father's forehead knowing how to use Linux. As a matter of fact, until I switched I was a Mac user.

And FWIW both my liberal-arts brother and his liberal-arts wife are now using Linux. My sister-in-law discovered the command line within a week.

I won't deny that there are things which are painful in Linux. But are they more common than painful things in Windows? I had to get a Windows machine to do some work on, and it's utterly terrible. I don't just mean the 'this doesn't work the way I'm used to' stuff: that's to be expected. I mean things like randomly prompting me for a smartcard PIN over and over again, when Linux would ask but once. I mean things like wanting to download OS updates as one large file, rather than many small files — which can mean that it's impossible to update the OS on a small disk.

I've not used macOS enough in the last decade to really have a critique; every time I use it, I want to hurl the computer through a window, but I freely admit that may simply be down to unfamiliarity, which is no more a critique of macOS than it is of Linux. It is annoying that I can't use a tiling window manager, though.