It’s already a reality, I was doing it about ten years ago.
require.js was a big piece of the puzzle, allowing the use of modules in browser without a build step.
The only time a “build” happened was to concat/minify scripts for production release, but even this wasn’t strictly necessary.
There were other pieces involved, but we had a powerful stack (aforementioned modules, css preprocessing, reactive templating) that had a faster and easier workflow than anything happening today.
I don't know anything about modulating LEDs, but could that high freq. have anything to do with the quiet but audible whine I hear when the light is on? Seems like it could be 8kish.
The idea of impossible fingerings is ambiguous - I can play that D minor voicing in that position as 2 - 4 - 4 - 3. It'd be interesting to see if you could take a set of samples from the user first and apply that to your algorithm. Also useful would be something that purely takes a set of pitches as input, and produces fingerings with the same pitches across various fretted\open strings (and possibly allowing for octave transposition).
This is the problem with "knowledge by web article" in general, isn't it? Blindly following best practices, rather than developing any true understanding of the task at hand.
What is a "level" of security? If I'm able to inject arbitrary code into your page, with it I can access your local storage data, but I can't access your "http only" cookies - so there's at least some "level" of difference.
Hi HN - I'm working on this more as a project than an actual startup, and would love to get feedback. It's similar to other sites that will grade your resume, except that it's tailored specifically for programmers. Right now it only handles resumes in English. Try it out and see if you learn something useful, thanks!
Hi Hacker News - this is a project I've been working on to see what might happen if you try to extract information from technical resumes. Any feedback would be appreciated!
Those are classifications, but are they definitions? It's still not clear to me that "stability" has much to do with the software performing in a consistent matter. Either way it's a careless choice of wording, I've never encountered anybody who saw the word "unstable" attached to a node.js release and understood that it might refer to the API (see surrounding comments).
This sort of "complexity" (DI, ORM, extensive configuration) has existed for a long time, particularly in the Java webapp space.
You don't need a license to release a framework, and a framework doesn't have to be sensical to be adopted.
If you learn the fundamentals of the things you're working with, particularly HTTP, web browsers, the web in general, and your chosen programming languages, things will become much more clear.
require.js was a big piece of the puzzle, allowing the use of modules in browser without a build step.
The only time a “build” happened was to concat/minify scripts for production release, but even this wasn’t strictly necessary.
There were other pieces involved, but we had a powerful stack (aforementioned modules, css preprocessing, reactive templating) that had a faster and easier workflow than anything happening today.