skysight-inc/HackerNews huggingface dataset:
> The docs are weak

The docs are more than weak, for something that's supposed to take over the world in 2 years I can't even click half the links in the FAQ?

> Just like there are no errors in binary, there are no errors in tree notation.

You can make any format "no errors" with little effort, the problem is not creating garbage data in the process.

> Tools can operate on binary without understanding the semantics. Tools can operate on tree notation without understanding the semantics. This is very powerful.

And there are infinitely many representations which can take this form. The problem is all such representations are no different than each other. I.e. tree notation can't represent anything binary can't. To actually do anything new you need to understand the syntax so if the main selling point is "are syntax accepts anything" well so does a million others before and after. The question isn't "how can generic encoding work" it's "what does Tree Notations syntax do that others don't already".

> All of the other notations listed have both syntax errors and semantic errors. Tree notation eliminates the entire category of syntax errors.

But they aren't eliminated at all they are just hidden to produce garbage later on instead. In S-expressions if I randomly drop a parenthesis I have mismatched syntax. In Tree Notation if I randomly drop a newline I have some completely different piece of data that validly represents garbage. The issue isn't eliminated just because it parses and this isn't the first format that can hold arbitrary data!

.

In the end though what is this beyond yet another form of S-expression? Is there something it does that a simple replacement regex would generate an invalid S-expression? If not why blow smoke up everyone's ass instead of just saying "Tree Notation is a S-expression format that uses whitespace instead of parenthesis"?
Current momentum is in liveview. I'm actually eagerly waiting for that to get up to a good version after the early adopters.
That depends on the link size. But I guess it may very well be better to have a big enough DC link and have it automatically modulate power all the way up to maximum and then keep it there, instead of tripping.
I don't think too many people actually care about all that.
People stop using Firefox because enough sites just plain don't work on it, and it lacks browser extension parity. Fix the actual browser and users will stay. Continue being too clever with the rendering engine, and people will continue to abandon it.
Depends on the situation. I worked on a site for lawyers and we needed to make it work in IE11, because that was the site all the lawyers used.

I was just at a bank the other day and saw IE being used. It is still 8% of the wider market: https://www.netmarketshare.com/browser-market-share.aspx?opt...
Formule 1 Grand Prix Belgium Live Kijken
https://www.asppa.org/forums/general-discussion/formula-1f1-belgian-grand-prix-2019-live-stream-0

https://www.asppa.org/forums/general-discussion/formula-1reddit-grand-prix-de-belgique-2019-en-direct-streaming-reddit-%E2%80%93

https://www.asppa.org/forums/general-discussion/f1reddit-grand-prix-de-belgique-2019-en-direct-streaming-reddit-%E2%80%93-formule

https://www.asppa.org/forums/general-discussion/f1tv-grand-prix-de-belgique-2019-en-direct-streaming-reddit-%E2%80%93-formule-1

https://www.asppa.org/forums/general-discussion/f1direct-grand-prix-de-belgique-2019-en-direct-streaming-reddit-%E2%80%93-formule

https://www.asppa.org/forums/general-discussion/direct-gp-de-belgique-2019-en-direct-streaming-1-sep-2019

https://www.asppa.org/forums/general-discussion/2019direct-fr-izlegp-de-belgique-2019-en-direct-streaming-tv-gratuit-live

https://www.asppa.org/forums/general-discussion/formule-1-fr-izlegp-de-belgique-2019-en-direct-streaming-tv-gratuit-live

https://www.asppa.org/forums/general-discussion/direct-gp-de-belgique-2019-en-direct-live

https://www.asppa.org/forums/general-discussion/direct-gp-de-belgique-2019-en-direct-live-0
Severe sleep deprivation can cause auditory hallucinations and other problems so first trying to help them get sleep to see how it affects their symptoms is a good idea.
The 2015 attack on Ukraine power grid (https://www.wired.com/2016/03/inside-cunning-unprecedented-h...) may be relevant here.
Definitely. We use seasonal demand peaks to learn how to cope with extremes. But if we didn't have those plus strikes I'd definitely be planning a few test runs.
Does that complete consistency include simulating a lightning strike to a transmission line?
P.S.

1. The very large Coq/Agda texts are usually large because of the proofs, not the specification/propositions. There's a 5-10x ratio, if not more.

2. I don't think that TLA+'s theory is intrinsically more "straightforward" than Agda's, even though it's certainly more familiar (I know some people who would insist that type theory is more straightforward than set theory). I think that a lot of work has gone into making TLA+ relatively easy to grasp; I think it's more design than a specific choice of theory, although the choice of theory certainly affects the design. In addition, as I've already mentioned, I think that TLA itself (i.e. not the set theory in the "+") is a particularly beautiful theory for talking about computation and discrete systems, that has some obvious advantages over the lambda calculus; in particular the abstraction/refinement relation that's the core of TLA (the semantic domain of TLA is a Boolean lattice where the less-than relation is behavior refinement).
Nearly everything is for sale, it is just the matter of the price. If Greenland can’t be bought for 250 billion, how about 10 trillion? Or exchanging it for Alaska? Or Hawaii? Granted, these options are not that lucrative, but they establish the price points from which one could negotiate to the mutual benefit.
It has changed from treating them as sacrosanct and precious (although some of them are), to treating them as a collection of blog post and articles.
So now whenever I start reading a book, I just try to skim through it initially. If there's an interesting chapter or concept, I will read it thoroughly. Yes sometime, you might miss some interesting concept while skimming but that's ok. It's rare and pros outweighs cons.

I feel there's so much abundance of knowledge out there that it's important to curate what you read. Sometime you can read the entire book in a day. Sometime even a single page might take you days to read and understand. So it's also about the density of knowledge and content in a book.

Also, sometime, I will read multiple books in parallel based on my requirements or mood. One thing that does help is your highlights/notes (both digital/physical). Having some system to refer back in future always help.

Yes, you will still forget a lot of what you have read but that's ok. We tend to remember the important stuff. And in future if we want to gig deep, we can always come back and read again.

Some of these concepts are also explained by Naval Ravikant in one of his interviews. So you can also watch them.
Lots of Craigslist computers are bought with stolen credit cards
Also buggy firefox extensions that will crash firefox or eat up resources.
Top Productivity Principles for Any Developer
I fully agree, the (meta) point here being a reflection on the environment where quoting wikipedia's description of a disney character can legitimately feel politically charged and facetious.
I've been professionally maintaining large deployments (thousands of machines) using systemd for years now, as well running systemd on my Linux desktop for as long as upstream has defaulted to it, and I can't recall a single bug or a single negative business impact from tying too many features together. I recall on multiple times wanting to upgrade but I'm pretty sure it was always because I wanted fancy new features, not for a bug.

(That's not to say systemd has no bugs. I expect it does. We either just didn't run into them, or we tested whatever complex thing we wanted to do—far more than could be expressed in any other init system, process keeper, or systemd competitor—found it didn't work, and moved on. That would be indistinguishable from systemd intentionally not having some fancy feature, and it definitely didn't affect us in production.)

Meanwhile, I can remember numerous concrete bugs in the Linux kernel, concrete misfeatures, and downsides from having a monolithic kernel where if one thing goes south everything does. But nobody warns me to avoid Linux....
Yeah, LV is definitely worthy. I'm excited for it too. Once LV drops with debounce / file upload support that will be enough to get me to incorporate it into an existing project.
Agreed, but it’s recursive nature does make it appealing in ways other ratios do not.
I don't know what you're doing to start your web/app server, but for eg. apache httpd it's a matter of

sudo apachectl start

(and likewise for all SysV-like startup scripts). For node, it's

node <yourapp.js>

(or rather using node-forever or node-cluster in prod). If you want to have it started on boot automatically, you put that line into your startup script. It doesn't get any more simple and transparent than that.

Why would you be sad if Debian and RH diverge? Linux started as a one-man show and became a huge community effort because it could run a wealth of F/OSS software. If you want a single-vendor OS, there's Windows, Mac OS, the BSDs, and others. Or maybe IBM RHEL in the future.
A reminder that some of the authors make money from pushing their anti-Psychiatry views.

For example, this conference on the Power Threat Meaning Framework (and alternative to diagnosis) is charging huge amounts of money for their conferences.
Well... they did tried firefox mobile.

Which failed but somehow found a new lease in life in 3rd world countries now. https://en.wikipedia.org/wiki/KaiOS
What kind of app are you looking to build?

If it is a general purpose application, I'd look at learning rails (this book was great for me: https://www.railstutorial.org/book ) and host on heroku.

If it is an API driven application, I'd look at using a tool like Zapier: https://zapier.com/ or Transposit: https://www.transposit.com/ (full disclosure, I work at Transposit).

There may be some low code/no code solutions for mobile apps, but I'm not in that space so not familiar with them.

Frankly, depending on your app, you could do a lot with google forms/typeform and some manual behind the scenes work: http://paulgraham.com/schlep.html

Again, it all depends on what kind of application you are trying to build.
Funny, I come from the opposite direction. I've been using Linux¹ and FreeBSD since the early 1990s, and was using UNIX since the mid 80s (SunOS, AIX, ...)

I find it really easy to deploy things in the cloud. I especially find it easy to fix cloud deployments when they don't work, compared to my cloud only colleagues.

If we're not careful, I think we might start to lose some basic OS level skills.

There are stories, perhaps apocryphal, about certain tribes of South American natives who find axe heads discarded by another tribe and see it as the work of the gods.

They don't know how to make their own axe heads, and see them as mystical objects.

It's not anyones fault for not being born early enough to have ridden Linux from its infancy, but I would encourage people to learn the basics of the OS.

Putting together cloud offerings, that's only product knowledge.

1: https://en.wikipedia.org/wiki/Yggdrasil_Linux/GNU/X
Chaos monkey for your electricity grid!
Fires Globally Have Declined 25% Since 2003
No, they are discrediting psychiatric evaluation. They're clear that any diagnostic process is a sham, and any attempt to supply a diagnostic label is unethical. They don't believe any psychiatric diagnostic label is valid.
The whole pizza.
> WASM is a vm and JS is a language.

I'm talking about compiling to WASM vs. compiling to JS. Calling something a VM or a language is mostly a matter of convention. x86 machine code can also be viewed as a language, and compilers certainly don't care. A compiler translates code in one language into code in another (there is no precise definition for "transpile", which is why compiler people hate that word; colloquially "transpile" just means that the compilation's target language is considered to be at a similar abstraction level to the source).

> Why would anybody want to implement it in Javascript?

Why would anybody want to implement it in WASM? If it's so that it could run in the browser, then compiling BEAM bytecode to JS would achieve the same goal, be easier to write and would likely result in a smaller and faster deliverable.

> Also BEAM GC isn't some generic GC, there's tons of crazy work going on with it to work with the Actor concurrency model.

There's nothing crazy going on in BEAM. As far as VMs go, it's near the bottom in terms of sophistication.
Just wanted to chime in with my experiences with the mouse. I never had any RSI since last winter. Basically my whole life I used some sort of ergo-like, lightweight large gaming mice. Sometimes very cheap ones. But on my new workspace I got a quality, yet slightly uncomfortable wireless mouse, medium sized so it can be carried around. Few months later I developed a strange pain which was going away during the weekend. Long story short, i reluctantly borrowed, later buyes, a Logitech MX Master mouse, and it all went away. I use it still. I say reluctantly because of all my gaming mice I perceived this one as heavy and sluggish. But I've got to hand it to it, after hours of using it, there is no fatigue in the wrist or arm.
Server side rendering capabilities of X are a relic of the 90s that never evolved and never could evolve..

Because funnily enough, the network transparency of X is in direct conflict with the evolution of GUI applications and toolkits: if a new server-side capability is required, it would only be present in a new version of the X server, and when the X server is remote… well, it could be anything, it could be an ancient version on a system that will never be upgraded, or an alternative implementation like VcXsrv for Windows.
Corbind 1.1.0 – Coroutine Binding APIs for Android UI Widgets
There’s two ways to build faster: more people or cut scope. For startups with limited resources, cutting scope is usually the answer.

When you say “extensive app”, that is a red flag for me.

I would focus on cutting scope and having the app do one simple thing really well. You don’t need an extensive app - you should build something smallerish quickly and iterate on it.

To answer your specific question about the platforms without code, I’m not sure.

Hopefully cutting scope can help you launch quicker (maybe on thunkable) to give you a product to help convince mobile engineers to join your team.
Computer displays being low is fine. The eyes and head are evolved for looking downward, and the lower part of the field of view makes both convergence and focusing on nearby objects easier.

People just need to remember that they can swivel their eyes without rotating their whole head/neck downward. You want to sit in a non-slouching position, with neck and head straight. The spine is quite good at supporting the weight of the head when the torso and head are straight. But holding up a tilted head for a long time puts a lot of static strain on neck muscles.

Personally I would recommend putting the top of the display at least slightly below eye level, pushing the display as far away as is comfortable (the further away, the less work the eye muscles have to do), and tilting the display backwards at the top so the center of the display points at the face.

Putting the display very high up in the field of view (like the article author’s pictured setup) encourages slouching and tilting the head back.

* * *

> If you hold your elbows at a right-angle, your keyboard needs to be just below your hands in order to keep your wrists straight. You want to aim to hover, not rest at an awkward, upwards angle.

Holding the elbows at a right angle is not something to prioritize. It’s fine, if the furniture allows, but if not, allow the elbows to be at whatever angle they need, and highly prioritize the wrists. IMO the most important RSI-preventing step to take is positioning/orienting the keyboard so that the wrists are not extended or flexed while typing.

> [watch out for a] wrist-breaking upwards slope. I don’t know why exactly this is (perhaps it’s inherited from mechanical typewriters needing their keys in the correct place), but most keyboards slope upwards, causing your wrists to bend as you type.

An upward-at-the-back tilt to the keyboard is not just okay, but is strictly necessary when using a tall desk and low chair. If you use a down-at-the-back tilted keyboard with a high desk, the wrists will end up flexed, which is a really bad idea. The appropriate front/back tilt of the keyboard depends entirely on the height of the keyboard relative to the torso (which determines the orientation of the forearms).

If the desk can be lowered or (even better) if a tall saddle-type stool can be used or if the typist can stand up, then letting the elbows be relaxed (more than a right angle is probably ideal) is also fine. When the desk is low relative to the torso, then the tilt of the keyboard must be adjusted to match the orientation of the forearms.

Dramatically “tenting” a split keyboard (aggressively tilting the two halves upward toward the center) will make a big reduction in static hand/arm/shoulder strain required. Separating and rotating the two halves are relatively minor by comparison.

Finally: the author of this article puts the keyboard very far from the edge of the desk, meaning that his arms are going to be reaching far forward. This puts a lot of strain on the shoulders. Pull the keyboard closer, so that the upper arms hang straight down, with elbows close to the body.
When I go to an Italian restaurant, I eat a whole pizza by myself. Size is roughly 30cm diameter. I can only assume that those two-pizza-team pizzas are either ginormous, or they're those American-style pizzas where eating more than 2 slices gives you an immediate heart attack.
This is the gist of it:

"The primary motivator for Lumen's development was the ability to compile Elixir applications that could target WebAssembly, enabling use of Elixir as a language for frontend development."

I had to dig to lean what BEAM is :)

"Bogumil Hausman next machine was called BEAM (Bogdan’s Erlang Abstract Machine). It was a hybrid machine that could execute both native code and threaded code with an interpreter. That allowed customers to compile their time-critial modules to native code and all other modules to threaded BEAM code. The threaded BEAM in itself was faster than JAM code."

http://blog.erlang.org/beam-compiler-history/

I now feel a little less bad that I couldn't figure out the acronym :)
> A lot of people in the psychiatric field believe that mental illness is due to chemical imbalances in the brain.

No psychiatrist believes this.
Thanks for the reply. I'm writing a ts parser and stumbled over this.

The reason I find it strange is that in this case it appears detectable that the return type will not match (independent of the any type in the parameter).

Is there a reason not to check this I'm not seeing?

By the way, I am quite amazed at the quality (and depth) of the typescript type inference & check model (despite it being "not sound" to quote you).
I agree that we've reached "peak phone". The newer models don't have any features you particularly need so keep using your existing one as a commodity until it breaks. The sales cycle is now looking like it's supposed to skip a generation of users. Unless you are getting it for free that 1000 or 1200 dollars you spend on a flagship could be used to enhance your life, either through having more disposable income, a holiday or investment. Enjoy your life and don't be a slave to devices.
To piggyback on mooreds - you need a baseline to see what your target market uses (if you’re making the business decisions)

An easy answer is to add Google Analytics to your site and support browsers that account for greater than 0.5% of your visitors
Sadly (but understandably) typeof is a runtime expression.
> it being open source and GPL, anybody can use it or fork it

The entire point of the EEE strategy is to capture protocols or standards, such as software developed by other companies or free software developed under the GPL. Forking isn't a relevant option, because the other parties software is not changed (it's expected to not be able to change).

From Microsoft employee Ronald Alepin's sworn expert testimony[1] in Comes v. Microsoft:

Q. Okay. And now, again, for the Jury, what does embrace mean in
this context as used by Microsoft employees?

A. It's used to indicate a strategy where Microsoft will embrace
the standards or the specifications and interfaces of another
company's software.

Q. Okay. And what does extend refer to?

A. Once the specifications have been embraced, then Microsoft will
extend them and add additional interfaces proprietary to Microsoft.

Q. Okay. When you say add additional proprietary interfaces that
are Microsoft's, what impact does that have technologically to
other ISVs and OEMs?

A. Well, the result is or the impact is that what was once sort of
community development property, the work of the industry and
industry participants is appropriated essentially, is taken over
by Microsoft.

And then Microsoft takes it and with its proprietary extensions,
makes it essentially unavailable on a going-forward basis to the
industry participants who were responsible for first developing
the specifications and the standards.

Q. Okay. And when Microsoft makes those APIs unavailable to certain
ISVs and OEMs, what's the impact to those ISVs and OEMs of their
ability technologically to create products?

A. It reduces their ability to create products, especially products
that will interoperate with Microsoft's products.

Examples of this strategy include Mirosoft's attempts to capture the Kerberos protocol and Java. In both examples Microsoft first embraced existing software outside their control by writing their own implementation, then added non-standard features that were only available in their implementation and a clause in their EULA that forbid anybody that used their implementation from re-implementing the features in other (original) software. The GPL doesn't help here, because Microsoft never touched the original free/open implementation, which continued to exist but was now incompatible with Microsoft's software.

While the systemd situation is a little different (it isn't trying to take over "another company's" software, systemd de facto IS somewhat similar to the EEE strategy. They initially embraced existing open standards common in Linux distros, and then extended various parts of their implementation intentionally[2] incompatible changes that had the de facto effect of "reduc[ing] [the] ability to create [non-systemd distros], especially [distros] that will interoperate with [systemd]"[3]. It's not exactly EEE, but there are strong similarities with new features used as a barrier to interoperability.

[1] http://www.groklaw.net/articlebasic.php?story=20070108020408...

[2] e.g. GNOME depending on the systemd-specific version of existing features that made running GNOME without systemd very difficult.
By no means am I implying that you offer negative intentions by your comment, but the “beneficial to all parties involved, and consented to by all parties involved” line was once how some described the system of chattel slavery in the United States. Let all actors speak for themselves.