HN user

billybolton

6 karma
Posts1
Comments30
View on HN

It is useful, you don't need to worry about insects and infectious diseases. Most pesticides are damaging to the surrounding ecology. Moreover, with the way industrial farming is currently done, most plants are genetically similar to each other. This means that if a bacterial outbreak were to occur, it could potentially wipe out many crops. In an enclosed environment, you eliminate these things. Although, you could still do it in a green house.

Only once for the containing canvas. A direct access to the canvas pixel data and webGL offscreen rendering is all you need. With a few hacks, we're already 90% there. I expect by next year to see an explosion of this. There already are projects in Github that translated SDL and OpenGL to build web widgets.

Forcing the DOM, JS and CSS was a mistake. The problem was that you couldn't have alternatives. wasm is going to disrupt front end by allowing you to have a strong typed language that you can use to build your own framework like the good ol' days.

It's a shame, they used to be good. I really like the idea behind Assassin's Creed. And Sands of Time is a god tier A++ game.

Speaking of Ubisoft, is it just me or do they repackage the same game with different skins over and over gain? I swear Assassin's Creed, Far Cry, Ghost Recon and Watch Dogs are the same game with different skins.

I'm not that attached to the Disney IP at all. I don't care about Pixar, Mickey Mouse, Starwars or Marvel. I'm very attached to video games, especially from the gamecube/ps2 to the wii/ps3 era. That was my childhood, Halo3, Bioshock, GTA San Andreas, Mario Galaxy. I got recently into more retro games from the N64/PS1 era, and I absolutely love those, they have this charming simplicity to them. I just don't feel anything for Disney, didn't grow up with it.

Nintendo, unlike most companies are focused on making games with gameplay. Most companies are making movies with gameplay segments in between.

It's not for games. We are dealing with big data, we need to highly interactive UIs on the web that we can use to communicate and interact with this information. Something like this is where I see the future of web: http://globe.cid.harvard.edu

That is not real time, but very difficult to pull off on web (harder than using C++ on desktop! Debugging webGL in JS is a nightmare). I don't see any issues with an ARM processor. The Harvard globe project if done in C++ could definitely run on a 2004 era computer. Most phones these days are much more powerful.

Incidentally, it would make the browser vendors themselves fairly obsolete, which is probably why it hasn't happened yet.

Mostly, but not entirely true. It's been a while seen we've seen a new browser come out, but the time is ripe to begin work on one, and release it in a few years. Just fork webkit to maintain backwards compatibility. I see browsers just becoming a sandbox virtual machine with a key ring, with minimal functionality.

Apple has the strongest incentives to build what I am mentioning. Not sure if they will.

I am doing something similar. The problem is not just HTML/CSS it's also JS. You need a strongly typed language, and have a scripting language on top. What I'm doing now is a Rust based framework, with an Erlang like scripting language to define complex interactions. Taking inspiration from Flash, all animations and transitions can be keyframed with tweens. Taking inspiration from the C/C++ to python interoperability, I want the same with Rust and Erlang. Now my entire backend can be written in Rust.

Unfortunately, I'm not open sourcing it. Not until I get a proper graphics context, and implement my own rendering engine. I think web assembly is going to revolutionize the web. I see browsers allowing you to cache common libraries/assets, and html/css being replaced by several competing UI paradigms. The one I favour is inspired from functional reactive paradigm, but there are equally valid alternatives. I don't think there will be a single frame work to rule them all, just competing schools of thought. Right now the web doesn't have any competing paradigms, just html, css,and js.

Reason web sucks: HTML/CSS are not suited to define complex UIs with intricate layouts and complex transitions and key frame animation. This problem was better addressed 30 years ago. Look at the menu UIs in games from the n64/ps1 to ps2/gamecube era (I'm talking about the game menus, not the game themselves). Some of them had far more impressive UIs than the webpages of today. This type of UI is an order of magnitude harder with html/css than just doing it all via X11 and C (even with memory management concerns).

The reason for this is that HTML first isn't strongly typed. If you make something complicated, and make a small change, it messes everything up. Your compiler can't help you. HTML tags are somewhat inconsistent. React, Rails etc. are all trying to address this problem. They are all taking inspiration from android, iOS, QT and gtk+ to make it somewhat component based. However, you fundamentally can't achieve this. HTML is in a land of its own, when you create an HTML tag, sure you can wrap it in a JS class, and mimic some of the characteristics that desktop frameworks provide you. You won't get the whole thing. I've seen many times different frameworks reinventing html templates (like handle bars). Templates can't solve all issues.

CSS sucks. The first thing about css that sucks is the "cascading" part of css. It should just be ss. CSS was originally designed to limit bandwidth by having it cascading. That's not the case today, and it messes everything up. The second thing that sucks, similar to why html sucks, is that again css is in a land of its own. It's hard to control css from JS (for interactive site you want this). I'm not even going to talk about how hard it is to position things properly via css when you are building layouts dynamically.

JS just sucks. I don't think I need to elaborate, I've mentioned enough points already.

Every single web framework out there is trying to address some aspect of the problems I mentioned, but my claim is that you can't solve it, you need to start over. Imagine if CPU makers made crappy inconsistent assembly code. Every year a new compilers and languages come out that tries to fix their predecessors. The most logical choice is instead to ditch that chip maker, make a better CPU with a consistent assembly code. You can't do that with web, you can't ditch assembly(html,js,css).

It only took 30 years for the web to get web sockets, webgl and now wasm. I think in another 20 years we'll come a full and get the remaining amenities that modern operating systems provide.

The reason I chose Rust is because it's a low level language with strong typing. It's not quite Haskell, but good enough. Writing a web server and UI with Rust is very nice. It just connects to the backend processes with ease, and doesn't make things awkward the way npm does. I do a lot of low level numerical and mathematical simulations, all done in C/Rust with all coordination & distributed computing done in Rust. I want Rust to take over. The sequence should be: Erlang -> Rust -> C

I chose Erlang because years ago I saw how reactive programming is extremely useful for complex interactions in a AAA game I was working on. In a game system you have the play interacting with the world, with enemies. The enemies interact with the player and each other. The player can pause the game at any point, then you need to bring up a menu screen with its own interactions. I've seen this work flow done in many different ways, and by far the reactive paradigm is the most sane. This was done in a bastardized version of Lua and Lisp.

HTML and DOM is the current way that is forced on us. What if I had a better model? I can't implement it myself. The DOM was meant to describe documents, not interactive webpages. HTML and CSS never had to compete with other ideas or technologies, because you physically can't do it.

The DOM is a relic from the 90s that refuses to die.

No webassembly is a solution to it. JS just sucks. Actually so does HTML and CSS. The entire web ecosystem is a closed platform. The reason that the front end stack is constantly bloated is because JS,HTML & CSS are awful. If the people behind wasm were smart, they'd allow generic handles to a graphics context so that people can write/export other rendering frameworks. Strong typing is good, reactive programming is good. Using html and css strings is idiotic, and we couldn't build alternatives to this model for the past 30 years.

Experts aren't wrong at all. The experts that Silicon Valley likes to favour and pour billions of dollars in are completely wrong, and it's funny how these best of the best are completely ignoring advancements that have taken place in niche fields over the past 50 years. Your so called 'experts' aren't even asking the right questions. They are all doing the exact same thing over and over again, expecting a different result.

Luckily there are extremely bright experts in other fields that do know what they are doing. But because they don't have the 'Harvard', 'Stanford' or what ever elitist label, they get ignored, and remain obscure.

Traditionally, "science advances one funeral at a time".

80%-90% accuracy on your arbitrary data set is meaningless.Your cute NLP algorithms suffer miserably in real life. You are severely underestimating how complex language is if you think getting a high accuracy on these narrow tasks is a meaningful measure of progress. Language is a big open problem for cognitive scientists, and linguistics alike. What makes you think that these computer scientists are magically further ahead of these scientists to create true NLP? Alexa is shit, Google Duplex is shit, Siri is shit. All these NLP applications will continue to be shit, until we actually understand what language is and how it works.

Luckily no one needs to worry about Google ever creating advancements AI (they can't, they lack the required skillset). Google is the modern day IBM, and AlphaGo is just another DeepBlue. I wonder when Google will make a gimmick like Watson. I guess Duplex is the beginning of it. It's amazing to see how many people were impressed by that. Then again, the tech scene lacks the scientific rigour that is required for spotting breakthroughs.

Chatbots are the next big thing. The reason they didn't take over is because NLP and AI sucks (and "sucks" is putting it very lightly). Current AI is stuck in a rut, and they don't even realize it. True innovation in AI will come, and surprise everyone, and like all innovations before, it will come from cutting edge scientific research.

Growing up with AI 8 years ago

I want something to new to come up and shatter Facebook, Google etc. We need more internet companies, and right now Facebook & Google reek with a vile stench. They lack creativity and innovation. They are the IBM of the current generation.