Stackblitz did this with Node (aka their Web Containers).
You could make a new project very quickly and prototype an idea. When finished, download it off the browser and deploy it.
67 karma · joined November 3, 2020
Stackblitz did this with Node (aka their Web Containers).
You could make a new project very quickly and prototype an idea. When finished, download it off the browser and deploy it.
There’s no free WiFi without requiring a phone number. It allows the government to connect internet users to real identities.
The way I’ve explained it is “unserious surprise” which also fits with this.
And then software that does exist will often have bugs for Linux that are overlooked due to how small the market is.
Whenever I'm onboarded onto new codebases, I have a tough time finding my own debug logs when there are hundreds of logs from different systems all cluttering the terminal. It's hard to know where one log ends and another begins. It's just white text on a black background.
I started this a couple days ago, but it's already been useful for my work. After building it, I found out projects like this had already existed. There's a section on bottom of the readme comparing them.
i.e. texting or calling a number in a specific way based on some standard tons of fast food places provide to make fast food orders without human interaction.
Upon review, it does not look like this is the case. I have several very low traffic projects on which would have never been anywhere close to the free limit. However, if I get involved in a random spam attack, it seems I could be on the hook for several thousand dollars.
This is incredibly dangerous. Netlify is often used as a beginner friendly free tier for static hosting. Not as something that is cheap, but as something that is free. This is just an overall dangerous position to put people in.
From my understanding, there are 3 answers here.
1. Most spaces do not need WASM. You don't necessarily see speed improvements since usually your JS and WASM (in the browser) are compiled into the same thing.
2. WASM is very good at bringing tools to new spaces. The biggest limitation here is in both tooling and education. It is not trivial to compile something like FFMPEG for the browser. Improvements to the WASI standard are helping here.
3. WASM is starting to see use in different spaces. For example, as a containerization format for efficient sandboxing.
I don't know that their Wasm module is necessarily "broken", so I'm unsure whether my contributions would be welcome.
My initial motivation to learn WASM (as someone from a primarily web background) was that I had a pretty poor understanding of WASM in general and so I had a lot of difficulty working with WASM builds in just about any capacity other than a heavy JS wrapper.
There are aspects to how WASM works that are quite different from other kinds of assembly formats that make learning the basics pretty important. e.g. how memory is requested, provided, grown. How functions are received and exported. Capabilities of tables.
A lot of this might be abstracted by massive wrappers, but you're losing a lot in perf and debugability when using them.
I detail this a bit more in the readme, but it supports general JS notation for certain things.
Surround your search with /these/ to perform a regex match on the character. To match on the name instead you can use the advanced search tab which is accessed via the button on the top left.
I may also add glob notation though, since that sounds like a pretty valid use case.
I've only recently dug into the big world of Unicode, but when doing so, I found the tools available sorely lacking. Most were server-side or needed to be downloaded and had confusing interfaces and buggy behavior.
The solution was to build my own. Turns out it's super easy to just download a 1.9MB text file and parse it using JavaScript. The entire application is client-side, so requests are quick and technically work offline.
Right click a symbol to copy it. Left click to open more information about it. Simple Search is the default. Click the button in the upper right to do some more sophisticated filtering with "Advanced Search".
I'll probably make it a PWA once I figure out how to properly do cache busting.
On a different note, I don't know many people who are interested in Unicode lookup tools and/or those who use such tools regularly. I've added in features that I personally found useful, but do let me know if there are killer features you'd like for it to have.
It may have access to the window object, however, so if something important is there, if can probably mess with that.
I think this would be a fantastic text editor for anyone new to the terminal. Provides some syntax highlighting, a nice background, line numbers, tabs, and mostly familiar controls without a ton of setup.
I think there are still quite a few improvements I’d love for it to have, but this might be the thing I recommend to anyone first starting out in the terminal who wants a bit of a nicer editor than nano.