Hacker Newsnew | past | comments | ask | show | jobs | submit | more xtrapolate's commentslogin

> "Product: Everhour. HQ: Minsk, Belarus"


So Go is somehow immune from a similar fate? What's the reasoning behind this?


> "Memory management in Kit is manual (no automatic garbage collection), with some convenience features to make this easier."

I was curious, but there aren't any examples of this on https://www.kitlang.org/examples.html


I see there's no privacy policy, and no clear guidelines on opting out. Why? Privacy was the focal point of 2018, but you're somehow ignoring that altogether?


> "Because after a day of work, most people just want to see funny pictures and check their email and login to a bank account to pay some bills. They're consumers, not producers."

You're simply saying people want affordable technology. In that case, what is Chromebook's advantage over the competition? The market is flooded with cheap hardware, targeting those exact types of consumers.


> In that case, what is Chromebook's advantage over the competition?

Chromebooks are not about the price. There are plenty of affordable alternatives. They are about having to do zero maintenance.


Lack of malware and ease of use.


Numpy is fast thanks to having much of its code compiled as a native library.

They were purposefully working to reduce abstraction, since performance mattered from day one.

WASM is a huge step backwards in that regard. If you care about performance, just install Python on your box and "pip install numpy". Do you absolutely have to have it come in a browser now?


> "Part of an effort to make a Jupytr notebook-like environment without relying on server side code."

So there won't be any server side code, you'd just be downloading the entire Python stack and dependencies every time you want to use this through your browser. This time it will be WASM though, instead of x86/x64/pyc.

That we can, doesn't mean that we should.


Well, you'd download the entire stack indeed - but not every time. Your browser does caching too.


Plus, if it’s packaged as a PWA, it can run offline and seamlessly update the runtime in the background using a Web Worker.


It doesn't share the cache between the sites though. A local installation has only one runtime.


Absolutely; it's pretty much like installing an application that includes all its dependencies. Which, interestingly, is also the direction installed apps are moving towards somewhat, at least on Linux.


There's an advantage even if you're running it locally. Now you can just load up some static HTML + JS files in your browser instead of spinning up a server and then pointing your browser at localhost.


It would work on a Chromebook and a iPad also.

And yes I could pay for a Jupiter notebook hosted on some instance but I dont want to.


Maybe, but it might require more RAM and CPU horsepower than they provide in order to be usable.


That would be dumb, so why assume that would happen? You don’t download every picture on every refresh.


As long as it's framed properly it can be acceptable. Ie. You get to a page with details and a "load environment" button with progress bars and all.

Of course when it's like 50-100MB you wouldn't use it in some cases. But once cached you're golden for your repeat visitor audience.


I guess we need an in-browser package management like npm?


Just compile Debian to WASM and use apt.


Just run a browser in your WASM Debian to hit the same page.


The plan is to build something based on conda.


In-browser package management, combined with caching of common dependencies, yes.

Like npm? No.


Well I'm not really into JS web development, but NPM and a bunch of Node-like extensions would give you compatibility with lots of existing libraries.


> I guess we need an in-browser package management like npm?

It exists and it's called bower.


I can think of several scenarios where this could be useful.


> "Finally they let you hire some help and instead of getting busy helping writing tests and refactoring he starts thinking about the best way to throw you under the bus to your superiors."

Here's what actually happens.

By that point in a project's lifecycle, that's not what they usually ask of the new hires. People are usually tasked with fixing bugs/maintenance, and implementing new business logic. Both of which are extremely challenging and stressful when working on a project that comes with no tests, or documentation.

Your actual task as the new hire is to start generating more value for the company, but that's so much more challenging when you have no way of validating your solutions, no infrastructure to rely on, and no metrics or documentation to consult. At that point, being the new hire, you're taking a lot of heat for not getting things done on time - mostly through no fault of your own. At that point, "wanting to throw you under the bus to your superiors" is a very natural response - it's a defense mechanism, you're (rightfully) frustrated. You're between a rock and a hard place. At that point you're no longer doing software engineering, it turns to politics/coverups/fire-extinguishing on a daily basis. Can you not relate to that?


Do you seriously think they care about re-using a name for a throw-away non-classified project? People have better things to do with their time.


The idea of the NSA googling `lemon graph` then saying "Welp, looks like someone else already has it. Back to the drawing board", is actually pretty hilarious.


A different approach to decoding vibrations into speech, involving a laser microphone: https://en.wikipedia.org/wiki/Laser_microphone


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: