ybx

Sounds like it's based on Trident to me

To be fair, most Linux distros haven't followed the Unix philosophy for a long time.

While I don't consider myself a libertarian by any stretch, typically roads and utilities are two of the things that have pretty easy counter-arguments - make utilities free market (or something of the sort) and roads can be paid via tolls.

If you want something that doesn't have a good counter-argument, look at policing and contract enforcement (basically, a public legal system). That's something that can't be done very well by a private entity or multiple competing private entities.

Another problem without much of a counter-argument is looking at e.g. utilities and roads together (i.e. a monopolistic infrastructure with a non-monopolistic infrastructure). Roads are monopolistic because they control that land - in order to use it, you have to pay the owner what they want. This isn't too big of a problem because if you feel one route costs too much, you can simply take another route. Utilities on the other hand, can be provided by anyone, as long as they run the pipes, lines, etc. out to you. In itself, if you feel one utility costs too much, you can pick another utility. The problem comes with combining the two - typically to deliver the utility to you, they would also have to pay the road owner to run the lines along and/or make some agreement. So what happens when an exclusivity agreement comes into play?

Well, unless you don't want the utility at all, you have no choice but to either pay whatever fee they want you to, or move. When you move, it's possible an exclusivity agreement exists there too. One could argue that it's not any better the way it currently is (Comcast, etc.) however you couldn't make it better by making everything privately-owned without regulation, and you could make it better by going further towards the public side.

Something like that would probably be better off with Aho-Corasick, with is similar to a trie but ends up with more compact FSMs

This hasn't been updated in two years and doesn't support the latest Elm version (0.17), sadly.

You can make it enforce rules strictly over everything, rather than selectively enforce it on specific applications.

What would be really nice is if there were a system like how debian, ubuntu, etc. does it, and allow for official (and unofficial) mirrors

The idea is that we'll verify things as a community; not necessarily that we each have to individually audit things

This looks like something you'd find in a cult.

> If you don't see the contradiction between these two statements, I don't know how to help you.

Just because it's in a browser doesn't mean it's remote access. Javascript APIs can be accessed locally.

The best skeleton I've found (if anything, it does too much even) is Otto Chrons' SPA tutorial: https://github.com/ochrons/scalajs-spa-tutorial

That's what I've used for one of my projects and it's worked out pretty well!

The title of this post is the same as the Calgary Airport's IATA.

> It could be that those who use large number of dependencies just prefer less dynamic languages when dependencies are very explicit and manageable.

Tell that to anyone using NPM.

There's also https://www.kimsufi.com/en/

Yes, but the end result is the same

Someone in Mozilla came up with a language called LLJS, that took full advantage of and compiled down to asm.js.

It looked like it had some promise, since it wasn't nearly as heavy as emscripten, but I don't think much has happened with it since it was created.

HTTPS doesn't directly provide it, sure, but it's still a benefit you get when using HTTPS.

This is just pedantic.

> Money is an artifact of the state; always has been, always will.

This is patently false. Money has existed before states, and it has existed without states.

Forking isn't possible when the code is not there, and when the company that created/copyrighted the code is openly hostile to forks. By them releasing under MIT, this issue is resolved.

As for the manpower behind Microsoft, git has made it very easy to merge code from relatively similar source code - in the cases that they make large important changes, those can always be merged in, and usually without too much work involved.

The only way they could succeed with something like that would be for them to go closed-source again, in which case you're still better off than if they never went open in the first place because you still at least have some code to work from.

But the thing he's saying is that having io.js happen was possible. It's also possible in this scenario too.

This is actually incorrect. "kilo-" always means 1000, and computers are not given some exception. 1024 is a KiB, 1000 is a KB.

Because Visual Studio Code is more of a code/text editor than it is an IDE. It doesn't compare to regular VS with R#.

Sure, but you could argue the same for things like COBOL

You're angry because they properly measure base 2 data?

Even if you disagree on how proper it is, that seems like an extremely small and unimportant qualm.

immediate feedback.

Just search "Gobby text editor" on google images.

Nice!

The question is not whether or not you're as productive, but rather, are you more than 80% as productive as you were before.

Actually around 75%

You mostly disagree with him entirely?

That's why he said "paired with your"