skysight-inc/HackerNews huggingface dataset:
Systemd correctly implements the "noauto" and "nofail" keywords in fstab(5) that were added in 2008 in the way they have been documented since 2010: if neither of these is specified for a filesystem, then that file system will be mounted at boot time and a failed attempt to mount that filesystem implies a boot failure.

Util-linux-ng 2.14 Release Notes (09-Jun-2008)
==============================================
mount(8) supports new "nofail" mount option.

https://github.com/karelzak/util-linux/commit/abe3d704b6aeb6...

The fact that previous init scripts gladly ignored these failures does not reflect negatively on systemd but on those init scripts.

Since 2011, FreeBSD has the same options with the same behavior, except that "nofail" is called "failok".

https://svnweb.freebsd.org/base?view=revision&revision=22283...

Add a special mount option "failok" to indicate that the administrator wants
the system to proceed to boot without bailing out into single user mode,
even when the file system can not be successfully mounted.

By your argument, FreeBSD broke UNIX.
The web has always been sad. Pop ups, pop unders, blink tags, etc. All things old are new again (here’s looking at you, animated gif!).
Rock climbing is a really unique mesh of physical activity, community, and puzzle solving. If you find the thought of gyms boring but want to start getting some exercise, I'd definitely suggest trying it out.
That's great to hear. I am convinced you have talent for teaching. Wish you all the best.
So I'm wrong because you say so even though you agree with what I said? Got it.
I don't think I agree. We know that there are diagrams that come from category theory that behave very well, this is what statebox uses. It enforces certain constraints, so we pivot everything around this and see if we can recover some form of programming from it.

certain cases are still much better done in text and statebox itself is written in text, so nobody is claiming programming itself should be 100% pictures, but then again, I think it can be done and I think there is merit to it.

after all, text is also some sort of picture; on the screen but also in your head
There's nothing implied at all. They are blue collar workers. Their career is on the decline because the mines are closing and there aren't enough new ones opening up to simply transfer the existing labour force to the new mines. So you retrain these people for work that is available.
Typically that approach setups up jack as the primary device user and pulse as the secondary. Your setup involves a usb audio device in addition to what I assume is some builtin audio device on your desktop/laptop. JACK's server only takes full control over a single device, so it's possible that JACK took over something other than your Scarlett leaving a different routing mechanism to shuttle data from the Scarlett to it.

As that's a mouthfull, what may be happening is:

Dev A <-> JACK <-> Pulse <-> Dev B

If that's happening then you'd want to switch the setup to:

Dev B <-> JACK <-> Pulse <-> Dev A

or

Dev A <-> JACK <--+--> Zita-ajbridge <-> Dev B
|
+--> Pulse

Per the windows driver, I have no idea and likely neither do ALSA devs since the source is not available there. If the Scarlett driver is a standard usb-audio device, then it likely should be exceptionally robust and very similar across operating systems.
If you're interested in learning TLA+, the best resources are:

(1) Specifying Systems by Leslie Lamport (https://lamport.azurewebsites.net/tla/book.html)

This is the original TLA+ textbook (I myself learned from it) and is very thorough, but sometimes fails to differentiate between specs which are model-checkable and specs which are not. Since model-checking has become recognized as the main source of value from TLA+, this might frustrate readers who think "woah, TLA+ can do THAT!?!?" only to be disappointed. I still like it, though. You can get a free digital copy.

(2) The TLA+ Hyperbook by Leslie Lamport (https://lamport.azurewebsites.net/tla/hyperbook.html)

Unfinished and unlikely to ever be finished (Leslie has stopped working on it), serves as a good companion book to Specifying Systems. I believe this is the only resource for learning the formal proofs capability of TLA+, which I myself have not yet used.

(3) The TLA+ video course by Leslie Lamport (http://lamport.azurewebsites.net/video/videos.html)

Very goofy, very fun. When Leslie teaches courses to engineers in person, he uses these videos. They're effective.

(4) Learn TLA+ by Hillel Wayne (https://learntla.com/introduction/)

A free online resource for learning TLA+.

(5) Practical TLA+ by Hillel Wayne (https://www.apress.com/us/book/9781484238288)

I own this book, and it is a great introduction to PlusCal (a pseudocode-type language that transpiles to TLA+) and TLA+ in general. Highly recommend! Along with the video course, probably the ideal starting point these days.
I want to clarify the "full body workout" point. For one, it's not really a full body workout, and you disproportionately work out your back. This, along with an under developed chest can cause your shoulders to roll forward resulting in bad posture. Another problem if you find you have a dominant hand while climbing, which leads to half your body getting exercised more than the other side. This is usually your right half because setters are usually right handed and will set routes that lead to you working your right half more. If you get a massage, it's normally pretty easy for them to immediately notice this asymmetry. Like all exercise, try to find a balance. No one activity is going to be a catch all for your whole body.

The other points are pretty spot on. I just wish climbing gyms weren't so expensive haha.
CMU has a lecture series on youtube on GPU databases.

https://db.cs.cmu.edu/seminar2018/
I've looked at them briefly but I'm worried about vendor lock-in and unpredictable pricing. The pricing one is a big aspect if I'm wanting to sell something to a client as the pricing needs to be simple and predictable. Any thoughts?

Also, how well do these work with source control? I like having everything under source control for easy reviews and rollbacks.
Source? Can't find it
I wouldn't say this list is exhaustive, more like a good start. It's missing some of the breadth that you are likely to find in a good CS program. I'm not seeing much in the way of OS, networking, undergraduate machine learning, robotics, software engineering, or mobile application development. Adding the above topics would make this list more comprehensive.
Are you just going down my comment history and trying to misinterpret anything I say so that you can respond and feel good about yourself?

Are you going to run home to mommy and say "look I won the internet today!"
WebAssembly could become the universal crossplatform language and that would open up a lot of possibilities.

From writing a hybrid app and replacing all the native parts with it (so Node in Electron), to even writing everything with WebAssembly and using native GUI.

It is already possible to remove Node and Chrome from a hybrid app by using webviews and Swift in macOS and C# in Windows. We're developing a crossplatform app using that technique and it's awesome. With WebAssembly the native part could be completely crossplatform with comparable performance.

The only project I know that does this is NodeKit but it seems to be a bit abandoned.

https://nodekit.io/
We started our journey by trying to understand why ie9 had higher figures than ie10.

As we also have an analytics on the server side, we extracted a raw log. We used our existing tools that can filter "fake" or "foe" trafic by its behavior. We then manualy analyzed representative filtered samples (still by analyzing its behavior).

It took some time, but was worth it, because we found an opposite conclusion than GA: most of the real traffic ($) from our ie9-10 samples is on ie10.

So now the dev. guideline is: forget ie9 and make it not too ugly/broken on ie10. ;)

PS: We had to do a manual work of filtering because our tools do not filter all the traffic that we know being fake or foe because we often have false positive.
I though Georgi Guninski found several.
I haven’t used MIG much, but it’s always seemed like a security nightmare. It’s somewhat convenient, but the codegen part looks really sketchy and of course with separation like this it’s easy to forget memory management guidelines, etc.
> more about whether a secure system should allow user code to escape lifecycle management

Please stop trotting that tired old line out. It is simply untrue. Systemd does the exact opposite of providing increased security. If nothing else the greatly increased surface area of systemd makes for a less secure system.

The pwnie articulates a number of other ways in which your code and your behavior are actively reducing the security of Linux.
An open-source fabrication 1um process
Is it enabled by default? My source just mentioned auto-removal for PWA, which seems like a weird decision for local databases
Is in fact it was a massive wire-wrapped machine
My side project just broke $1k/month and I already count that as a success.

My success metric is "freedom". If this side project could net me $3k/month, it would net me a lot of "freedom points"

I reckon everyone has a different metric for success
Just a quick follow-up: I'm already working on migrating the data to DynamoDB which will automatically encrypt the data (https://docs.aws.amazon.com/amazondynamodb/latest/developerg...). This will go live soon. But the website will stay the same: I won't say I offer encryption until I have true end-to-end encryption.
Seconded. While this book has a lot of nice encouragements to simply coding and enjoying mazes, it also ships with two absolutely kick-ass appendices.

The first is a very short bite-size summary of all of the algorithms that the book has covered, so that you don't have to read through the entire book again to remember the differences between the different algorithms. This is so good I wonder why it is not a standard feature of textbooks in general, such that it has its own standard section name (say "Abridgement"). The key is that it's longer-form than an introduction or abstract or conclusion, but the freedom to occupy its own space allows it to be expressed in human terms, unlike the "real research" parts which have to be a bit more rigorous.

The second is a quantitative comparison of the different algorithms among different measurements, which again is like "why isn't this an appendix everywhere?" and such. It's still not trying to be absolutely rigorous but just to give a rough feel for the different options there.

As a result you can just grab the textbook as a reference, flip through those appendices, say "yeah that's what I'm looking for, longer twistier paths," read up a quick description of how that algorithm works, say "well that's a bit more involved than this other one which looks good enough, maybe I'll start from there."
Yeah definitely not how I would talk to the employee, but it's extremely frustrating that they don't get it. As a business owner you can literally be losing money on a deal and have the employee assigned to it tell you they want more because they're only getting X% of the total contract amount. Only way I've found to protect against this is to keep the operations team from having visibility into finances.
They were wire-wrapped but by robot.
Next year's tech will still be cheaper. If they don't have to retool for the next gen because they literally can't, then we can enjoy the economies of scale in producing the same tech over a longer period of time.

I also dispute the scope you assign to this "upgrade" cycle. It's a huge overstatement to claim that the whole tech sector would "collapse". The tech sector is far larger than phones and personal computers.
I know a guy who can talk to CEO types and keep them interested. That’s the skill you need.
I posted something similar in another thread about advice but take a programming terminology/vocabulary class, you probably know most of it after a few years experience but even a slight misunderstanding in diction can have serious implications down the line. I was surprised how much I learned and how beneficial it was to the conciseness of my code comments. This can be especially helpful with network stack and TCP/IP related work, remembering all the acronyms can save you a lot of time.
I've found mindfulness in powerlifting, as well as rowing and bicycling. Powerlifting is an acute condition - I have ~30 seconds of absolute concentration and focus, being totally focused on executing and knowing nothing else, ignoring the agony of screaming muscles and intense pressure. Rowing and bicycle are both much longer steady state, but at the right pace it really focuses you in to the here and now.
All very good and important advice for those entering the industry. I'd like to stress the people aspect even more. Treat people the way you want to be treated. If an engineer doesn't understand a certain technology, kindly explain it to them instead of berating them for being "not smart". The jerks will outnumber the saints, but being the latter almost always pay off (being successful, high status, generally liked by everyone else etc.) in the long run.
BuzzFeed’s Experimental Era Is Over
For those like me, and like many in the UK, whose maths education ended at 16, I can definitely recommend Khan Academy for learning or relearning pre-calc stuff. The videos are short, the exercises are well thought out and numerous, and importantly the UI is great.

For example: https://www.khanacademy.org/math/algebra/
Yes, just on power evelope alone so many unknowns that could influence other parts of a ‘done’ design.

I wish them well but I’m sceptical. Still, it would be great to be surprised.
MapD is now called OmniSci and is mentioned in Uber article. I bet Uber had a good look at MapD internals.
Perhaps a better messaging here would be - if you're working on gene editing, nuclear fusion, or some such radical and ambitious project, we want to hear. Tell us the path you took to get to this point, and your ideas for the future. Then select from everyone who writes in?
I've certainly seen this in biology. The rapid growth of molecular biology graduate programs in the 90s and early 00s lead biology to becoming a career path with a lot of mediocre talent entering graduate school. To keep research faculty happy and inexpensive hands at the bench, the historical filters for clarity of thought and careful logical analysis were reduced in qualifiers and dissertation defenses. Simultaneously, there was a shift from biological experiments designed to carefully test a hypothesis with a limited number of logical outcomes to genome-scale (e.g., gene expression) experiments that were more likely to lead to pattern matching and post hoc story telling exercises. This shift reduced the filter for careful thinkers even more. The overall trend lead to more hierarchy in the sciences, which has limited the number of topics, the acceptable answers, and the funding for carefully thought out, but non-mainstream research.

In biology, the complexities of the subjects are very high relative to physics, so determining the important questions is much harder. Studying bacterial immunity, which lead to CRISPR, was and is a very niche field, but led to a very important biological technology.
A good solution to that would be if the mobile app stores allowed PWAs. Instead of using Cordova or similar you could just add a URL with the PWA.

Microsoft already does this: https://docs.microsoft.com/en-us/microsoft-edge/progressive-...
I think the Amazon thing is gone, but I haven't used Ubuntu on a desktop for a while. It's ok on servers, despite the packages are not always current in this distro, but hey, who needs OpenSSL or OpenSSH versions which are not more than a year old.

It's sufficient for a rookie webdeveloper, but everything else is a pain in the ass. Oh, you need libsasl to compile this project from sources, it would be a shame if we rename it to sasllib (yeah, this shit is still happening!).

Long story short, get Debian. Or install Fedora if you are comfortable with.

In my case, I learned to work with Linux with Debian on my main PC and Slackware on my "project box". A lot of trouble, but now I can say I know what I'm doing (or why something got wrong).
After that I tried a lot of different distros and I found my match, I'm happy. So try something crazy, like Gentoo/Arch/NixOs/random-distro-listed-on-distrowatch.

BTW. Rolling releases are awesome
Very little actual science in the article, and the title doesn't support the vague assertions being proposed. Just more divisive content to pit us against eachother. That kind of content gets the most "bang" these days.
If you smell shit while walking down the street, maybe someone dropped a deuce on the sidewalk. If you smell shit everywhere you go, maybe it's you, maybe you shat your pants. When you violate the principle of least astonishment you're creating a huge stink.

That you can configure systemd to behave in a less obnoxious manner is well beside the point. Systemd should be unobtrusive and predictable without any extra action on the part of the distribution folks or end users.

That the suggestion is to simply read the code or documentation is the height of arrogance considering how sloppy and insecure the systemd code is (parse error equals root privileges? come on…).
Commercially, no, not at all. Snapchat looks successful too if all you're checking is MAU. And yet the company has been struggling constantly since it went public.

In the context of valuation and business decisions, it turns out having a lot of users isn't enough. If it was, Snapchat wouldn't be in trouble and we wouldn't even be having this discussion.

As a further point, note that you're citing 2014 and 2016 figures, and I did say, "especially in 2019." Yahoo never recouped its acquisition price from Tumblr.
Sql: Inner Join vs. Outer Join
I received my dev kit and immediately broke it.

The SOM connects to the mainboard with 4x 80-pin tiny connectors. If you miss the little warning on the silkscreen and lift from the wrong side, BAM, two broken connectors.

Purism said they would sell me a replacement SOM, but they're not really communicating now.
> I just wish climbing gyms weren't so expensive haha.

Think that's the case with any specialty gym. Crossfit, climbing, MMA/Boxing/BJJ all are very expensive.
Apparently the optimum information-theoretic alphabet would have e (2.718...) bits, but it's a little awkward to work with a transcendental base. The pain in working with trinary circuits is why we use binary instead.
> In JSON-format, AQL provides better programmatic query experience than SQL for dashboard and decision system developers, because it allows them to easily compose and manipulate queries using code without worrying about issues like SQL injection

Oh, right. Surely your "data scientists" and people that are familiar with a STANDARD Query Language would be better off using a SQL interface? Worrying about SQL injection? What sort of crappy codebase do you even have?
> The designer traces regions of interest in an image and annotates the regions with style parameters. They can optionally specify a solution path, which provides a rough guide for laying out the maze's actual solution. The system uses novel extensions to well-known maze construction algorithms to build mazes that approximate the tone of the source image, express the desired style in each region, and conform to the user's solution path.

Sounds cool. Is there a public implementation?
There's no obligation to give useful feedback. Just to not waste people's time with unuseful feedback. We want to maintain the high signal to noise ratio. If you don't feel like providing signal is worth your time, the correct alternative is not to add noise.
Thats a very good question. There were 2 main reasons for that. There are a lot of chatbot solutions to enable human initiated workflows while there were hardly any solution which enabled human in between an event driven workflow. But more importantly, since we came from a sales focused market and faced the problem of supporting human element within an event driven workflow ourselves, it was easier for us to get the relevant customer feedback.

Also, chatops right now is mostly human initiated and is focused on tech. We wanted to tackle enterprise integration market where the need seemed more immediate. A lot of the people we talked to hated logging into their CRMs and updating them at regular intervals can be a very tedious task. Hence we decided to prioritize event driven workflows with human in between, while keeping the architecture open to support human initiated workflows triggered from slack as well.
I guess the split (on there, off home) would kinda work, but it seems like half measure when I already have a road bicycle for serious rides and a motorcycle to get around the city.
there is some pretty solid theory on how to translate between the kind of diagrams statebox uses and digital circuits. In fact we are doing some experiments with direct diagram to wafer (chip) translation using LibreSilicon http://libresilicon.com/
this is certainly not a done thing, but something we'd love to work more on in the future
Teenager and His Mom Tried to Warn Apple of FaceTime Bug
A Mind At Play is an excellent biography of a fascinating mathematician and visionary thinker. Ranges from early life through final years and also does a decent job of introducing his Mathematical Theory of Communication, the basis of modern information theory. A solid 4½ stars.
> ...you draw architectural diagrams. ...Which allows us to interpret the high level architectural diagram to a low level program, by telling what exactly the nodes and arrows do

This is not a new idea at all - I'm strongly reminded of the whole Model Driven Architecture brouhaha back in the 1990s and early 2000s. Needless to say, it didn't work. You can't do "code generation" from a high-level architectural diagram and expect to end up with a functioning system! At best, if you really do it right, the high-level design might enable you to specify type-like properties that constrain the low-level implementation in a broadly helpful way[1]. But you still have to write all the low-level code!

[1] And this is in actuality incredibly optimistic - MDA and UML didn't even manage that! Instead, all the pretty diagrams (1) were inherently fuzzy, so they did not embody any actual constraints on the implementation, and (2) even in the best of cases, got immediately out of sync with the ground-level truth of the actual implementation.
Where can a regular end user get an LTSC version?

Last time I looked around the conversation quickly dissolved into piracy. Not sure if I was just looking in the wrong places though.
Great post about Node.js modules
I think those examples are a bit misleading in that nobody actually prints 100,000 lines of code and looks at them all at once. So those examples are showing probably the whole "program" at once, which is impressive and looks daunting, same as a big textual code base.

Rather, in order to understand a certain aspect of the system, I imagine picking just one of the nodes and then asking the IDE to show me, say, the immediate inputs. Some of these may be semi-hidden (code folding!), others may show more detail, etc.

BTW, I've been thinking it would be great if these systems had a textual representation in the vein of Graphviz' dot language. So one could have the best of both worlds. For diffing, a simple textual diff could do, but one could come up fancier semantic diffs in the same vein semantic diffs for code or XML exist.
Any benchmarks against traditional data warehouse solutions?
OSI weighs in on open-source licensing conflict
If you're capable of understanding TLA+ proper, is there much value in starting with PlusCal, in your opinion?

Is PlusCal more a gentle gateway or properly useful in real-world applications?

I lean towards starting with Lamport's book over Wayne's, because the latter seems very PlusCal-centric (and the layout and typography don't appeal to me), but that may be a mistake.