I filed a bug that this was not spoken about in the announcement.
It would seems like it will cause a lot of drama as this actually rolls out.
322 karma · joined February 3, 2012
It would seems like it will cause a lot of drama as this actually rolls out.
That looked like the way to do it but I haven't tried yet.
But thanks, that's actually a nice little machine.
4gig ram.
Nice screens, reasonable processing power but they throttle the ram to make you want to spend the $500-750 for the "power" of.... 8 gigs of ram. But with the bloat of a useless(to me) windows license included.
How long is the chromebook spec going to stay like this? It's awful and holding them back.
It's nonsensical in 2018 to have this little ram on a laptop,chromebooks included but there it is still.
"Dedalus: Datalog in Time and Space"
http://db.cs.berkeley.edu/papers/datalog2011-dedalus.pdf
Here is Peter Alvaro's Strange Loop talk -
https://www.youtube.com/watch?v=R2Aa4PivG0g
It was a shame that most people, seemingly the Eve devs as well, seemed to focus on making Eve a language for easy programming for the masses. Thats a huge wall of a problem with a limited funding slope.
I think if there had been more upfront work and focus on the distributed programming/database possibilities, that Eve would have founded an actual community to push it along.
Eve as a language for doing business logic against say Kubernetes? As a language to wire up ETL processes?
I think it could have found a niche that would have made it grow in power before trying to take on the mass market.
Just a thought.
People have no sense that they might want to look at something in 10-20 years in that web service that was so handy at the time...
I think however there is no "proof of existence" of any software or capability that would compel even early adopters to use a 100x100 display, even with all the other physical issues being polished to a high sheen.
Looking down at your phone or smartwatch seems far more likely.
The "maybes" that people frequently suggest require a staggering amount of unwritten software infrastructure (sometimes up to and including sentient AI).
Broadly, almost everything in it has been either not born out (vision concerns) or less of a problem then first assumed (motion sickness) once the limitations of different users were understood.
Many people using VR find that the vestibular concerns are not an issue over time as long as the framerate of the system is high enough (90fps+). People actually do get their "sea legs" over time and many (largely gamers so far) ask for locomotion systems that were considered terrible ideas even 2 years ago.
This is an industry where outsiders have a very limited understanding of the serious serious problems in front of AR.
It's also an industry that is taking advantage of the very limited understanding of just about everyone not in it to hype things far beyond their capabilities.
If you care about AR in even an offhand way you should spend some time self educating and Karl Guttag's site is a good way to get started.
It's very interesting field but there are tremendous challenges in front of it and it serves no purpose to just assume the companies involved have actual magic leaps that solve the problems.
What is your sense of the latency guarantees/scheduling to user space graphics and input? This is an area that everything else kind of fails at. "No drawing the groundplane and every possible frame for this user you have in your VR grasp is not optional".
Is the security actually in use or just someday?
edit: security looks baked in but tbd
I have no interest in the play store but I would like my lineageos/fdroid userspace available directly to my desktop.
It's pretty important to realize that a files position is merely it's default tag (and you can tag it further with many different types of systems like extended attributes, as I think both Gnome and KDE have used at times).
Without that default tag you have a mess.
It's also important to note that Tags have a very high maintenance cost of their own.
Duplicate, inconsistently applied and redundant tags are a aggressive cancer in any of these systems.
No you can't just ignore them as they make it more and more difficult to accomplish even basic viewing /scanning over files for the system and the user.
Many many users have trouble even doing basic maintenance on their file locations (that default tag) that makes a tag based system even more prone to failure.
I think some core primitives and conventions exposed at the language level would have developed it into a uniquely useful language environment.
This is the most important missing piece, are their bugs for this?
Until we have html/dom textures in vr I just don't see webvr being very successful.
Just like the headset isolates you from the room, the lack of normal web content in vr/mr is very isolating.
I don't believe github themselves will make a native client any time soon, and we shouldn't expect any other websites either.
Thus HTMLTexture seems critical.
-I don't know how the FF reader mode is coded-
Where is the "HTMLTexture" support (the hacks for it are janky and not viable in my experience)?
I think WebVR will not take off if it doesn't have a clean way to experience the web's existing 2d elements, not to mention even VR needs a way to do 2d layout.
Any thoughts? I know Chrome guys were experimenting a few months back and there was some talk of it being in WebXR...
With partial application in the mix, functions are in an almost indeterminate state (to the programmer typing at the keyboard even if some compilers know).
In functional styles, programmers are encouraged to "just pass a function".
The f(x,y,z) gets passed around in an unknown state of f(maybe needs x, maybe needs y, maybe needs z).
This would be complicated even if it was the same function with a declining arity as it was passed around. Several languages allow named arguments which just adds to the signature complexity.
It's hard to see the benefits of the complexification.
Most pedagogical examples of the use occur in tight loops where the complexity isn't obvious. Once a function is passed outside of that tight loop I wonder at it's actually utility vs the negative effects.
I could more confidently selfhost a web version of my calibre library for reading and bookmarking. Calibre has a web version but I'm not confident in it and would be uninclined to host it even in a sandstorm instance for example.
The memory issues of libreread, as indicated by others, are too much for hosting in a friendly way with other apps. The value of full text search isn't nearly good enough to warrant the memory usage. Aim for < 60MB serverside.
Calibre has an large amount of features that are critical for people actually trying to maintain an ebook library. Those features have been added and polished over a decade. I'm very doubtful they can be replicated in a reasonable timeframe.
Valuable to see people making things in this area though! Cheers.
#TabsToolbar {
visibility: collapse !important;
}
Don't have an immediate use but I like it.
https://discuss.kotlinlang.org/t/any-plan-for-supporting-lan...
Java seems usefully far along however...
Can't see any of them being worth putting a headset on.
Can't see any of them being worth launching an app on a phone to stare through a camera at.
Some of them need some pretty next level ai.
What are the useful applications for AR outside of verticals?
I've not seen anything compelling in the phone only incarnation.
The headsets have a lot of engineering issues ie many years to overcome.
Even with headsets its unclear the value of adding the visual clutter and noise that most ambient/immersive computing demonstrations seem to assume.
Whatever value you can add generally requires constant headset wear for it to be ready to hand. This puts even harder engineering problems on the industry as it forces super light and easy headsets (google glass was not AR nor a technical path to it).
Not seeing it yet.
What you are describing would stop the entire music industry from functioning.
I won't be using this as it definitely sets off my library-depth spidey sense.
The multiple libraries it abstracts would all change versions over time and lead my applications to be even more brittle.
Vuex being mainline with Vuejs is a major plus as I look at its long term stability, though whether it insists on vuejs I need to look into.