mpolun

mpolun

anno scorsodiscuss

[dead]

mpolun

anno scorsodiscuss

[dead]

mpolun

anno scorsodiscuss

[dead]

mpolun

3 anni fadiscuss

[dead]

mpolun

4 anni fadiscuss

mpolun

4 anni fadiscuss

It's for proper integration of garbage collected languages -- otherwise you need to embed your GC too, which bloats the wasm. JS host VMs have very good GCs these days, so hooking into them allows for better integration by e.g. go, Java, C#, etc.

Right now wasm is really designed for C/C++/rust

mpolun

4 anni fadiscuss

mpolun

5 anni fadiscuss

I don't see how it's any different than using any hosting provider. It's probably worth encrypting your databases, but if you don't trust your hosting provider you're hosed -- managed service or not.

If your paranoia is justified (which it may be, depending on your needs), you need to host the machines in your own datacenter

mpolun

5 anni fadiscuss

swc (https://github.com/swc-project/swc) is a rust equivalent to babel and has a bundler under development. Not sure how far along it is.

That would be an interesting comparison of performance and features.

mpolun

6 anni fadiscuss

It would be interesting to see a raw selenium comparison -- WDIO is slower with both backends, it could be that selenium and puppeteer are both about as fast, and the performance difference is mostly about higher-level framework.

mpolun

6 anni fadiscuss

Same with postgres. I never use specific lengths for text on postgres.

mpolun

6 anni fadiscuss

It's not part of rustup. At least for the VSCode plugin, it'll prompt you to download when it first runs. As long as you've got a working rust installation it'll work pretty seamlessly in my experience.

mpolun

6 anni fadiscuss

I don't think this is accurate. Other people may know better, but from my understanding the maintainers of ifconfig realized that to update it to use the new behavior, they would have to end up changing the output. The output of ifconfig is used by a lot of scripts, so changing the output would break a million users, so they decided to write a new tool, rather than add a flag or something to opt into new behavior.

So it's userspace compatibility, not the linux kernel compatibility that lead to a new tool.

(and linux will drop old interfaces if it can be proven that no one uses them, or if they're insecure)

mpolun

6 anni fadiscuss

You can only test for cases that you forsee and predict. The advantage of staging environments is you can see many of the cases you never predicted before it hits customers.

mpolun

7 anni fadiscuss

BigInts are coming to Javascript -- they're supported in most browsers and in node now, but they haven't officially been added to the standard.

mpolun

8 anni fadiscuss

Rust actually has that they just can't be substituted automatically because they're different types:

    fn<T: MyTrait> compile_time(thing: &T) {}
    fn run_time(thing: &dyn MyTrait) {}

The reason that you can't just substitute them is that you can do more with compile-time generics than runtime ones -- runtime generics have unknown size (different concrete types have different size, so what size is the runtime generic version?) so they always have to be used through a pointer (and usually heap allocated). There are a variety of other restrictions on trait objects (runtime generics) for type-system reasons.

It would be possible to find cases where compile time polymorphism is replaced with runtime polymorphism, but I'm not sure it would really gain much given the restrictions.

Now if you start changing the language semantics a lot more becomes possible, but I don't even know what changes you would have to make to the language to let that happen.

mpolun

8 anni fadiscuss

Software hasn't been getting worse -- it always sucked. It used to be fast and small because there was no other option.

Also:

> @jckarter: A DOS program can be made to run unmodified on > pretty much any computer made since the 80s. A JavaScript > app might break with tomorrow’s Chrome update

LOL, DOS programs were crazy nonportable. They usually can only be run in VMs these days. Comparing it favorably to the most stable and portable API (the js ecosystem is another story, but the browser APIS are super-stable and never break) in the history of software is hilarious. I mean, all the flaws of DOS programs are totally reasonable given their constraints, but the comparison gets this totally backwards.

mpolun

8 anni fadiscuss

Unfortunately this change has resulted in something very confusing: there's a stretch of 295 going to/from the PA border in NJ that is labeled 295 North, but will take you south (or you'll go north on 295S). Once you get into PA it makes perfect sense -- it changes to 295 East/West, but NJ between the PA border and the rt. 1 intersection is labeled the opposite direction of where you're going.

mpolun

13 anni fadiscuss

The main thing I wish google would take from apple, is not a place to show off and sell their devices, but an easy place to go get support on those devices.

mpolun

14 anni fadiscuss

I agree that raw callbacks can get out of hand, but the typical solution in js is to use an event emitter (http://nodejs.org/api/events.html) or promises (like https://github.com/kriskowal/q), the latter of which seems to be pretty close to what this article is talking about. Is there a fundamental difference, or are promises an example of functional reactive programming in a language without direct support for it?

Submissions

[untitled]

A javascript dependency injection framework in under 20 lines of code

Why and how to do dependency injection in javascript

Django and the Real-time Web

comments