Only on a low level, right? I have not been thinking about ram and disk in ages. I calculate with variables, I store stuff in a DB or in a file, I access the net via http. Nothing would change if ram increases I think.
> it is very unlikely that "we" could turn into an "I".
We share more and more every day. And the ones who participate in the sharing benefit. I remember when some people said "i will never own a mobile phone. i don't want to be reachable all the time.". They all have smartphones now. Todays kids not only have mobile phones, they have internet connected phones with cameras. And share their experiences online. Tomorrows kids will have google glass or an antenna implemented in their head. Realtime streaming their experiences into the heads of others.
From my experience, risk takers have the better life. On average. That doesn't mean you could not end up fucked. But that's the whole point of risk taking.
And for outside money - I have been screwed so often and so hard by business partners. Maybe it's just a personal thing. But if I had to give my young self an advice from the future, it would be: Don't entangle with others.
Oh, and I think you completely overdramatize this. Don't pretend you are preparing a flight to the moon. Just make a real minimal viable product in a month or two. And see if people use it. I have seen people with dedication going from not being able to program to having a working thing generating money in less then 2 months. Its all about going into it with 100% full force. If you tinker with a project on the side, my bet is that it will fail.
In the "getting started", you should put the .js and .css files somewhere so the examples work. I copypasted all your codelines just to be dissappointed that it doesnt not work. I understand you probably don't want to be a cdn. But for testing purposes, I cannot be assed to copy stuff over to my server. I prefixed them with https://golden-layout.com/assets/ and it nicely worked. Nice. Bookmarked.
Thanks. That might work. But it feels a bit unaccessible. Looking through the code also gives me a strange feeling. Too many dependencies. They should just give you a .js that enables certain functionality and thats it. Like "include brick-flipbox.js and you have flipbox functionality".
Plus most of the demos do not wort (tried in chromium).
Can I use this client-side? From what I read on the page this seems to be only geared towards a certain server-side-setup with node.js, brewer and stuff.
So we want to make payments via our phones. My first thought would be to create a protocol for this. Instead we get ApplePay and GoogleWallet and whatnot.
If the internet was invented today, we would have AppleMail instead of email and GoogleTrans instead of http.
Interesting. In fact, I do not remember that. I started using the internet some time in the 90s. I never used Compuserve nor AOL. I never heard about Prodigy.
Also it might not be necessary for the involved parties to get together. They could release different protocols. And then the lesser used will be forgotten (like gopher is forgotten today) and the more frequent used will survive (like http has survived).
So we want to make payments via our phones. My first thought would be to create a protocol for this. Instead we get ApplePay and GoogleWallet and whatnot.
If the internet was invented today, we would have AppleMail instead of email and GoogleTrans instead of http.