I remember the days having to build my devkits with power regulators and having to flash them with separate programmers. The Arduino ecosystem opened up hardware to many designers, makers and tinkerer's. sure thing, the real cost of the boards is low. but the value is tremendous.
It's also the only place with such amount of trains. It is quite involved of making the infrastructure, and still it's managed.
From april onwards you can travel from Amsterdam to London for 40 euro in 3 hours. There's a lot to align.
Doesn't take away from the things that could be improved. Trains from Amsterdam to Germany stopping in small towns doesn't help.
There probably will be a plethora of different hard issues to fix in such situations.
It's also easier to institute change in a dictatorship as opposed to a democracy (being a dictator that is :).
You could use the 'chromecast' flow. Where it creates a WiFi network the user has to connect to with another device. And then serving a webpage with configuration.
Funny thing is there's practically only Mozilla and Google left with their browsers. Microsoft, Apple and Opera all basically piggyback on the chrome renderer (prolly not entirely true for safari, but it doesn't run on anything besides apple anymore)
> Physicists say this futuristic, super-secure network could be useful long before it reaches technological maturity.
Isn't that what they also say about the internet atm?
When a PR isn't merged or closed within a couple of months at least, the project doesn't look healthy to me. It might still function. Just wondering what the reason of reposting this would be.
Why is all the GraphQL documentation so tightly coupled with either Apollo or Relay?
Apollo doesn't work nice with a non-react setup (imhe), not to start about Relay itself.
All the Relay server side stuff makes the client also really boilerplaty.
I don't think i'd buy this book, since it's also apollo stained.
Does someone have good resources on how to use vanilla GraphQL without the bloated Apollo/Relay stuff?
I'm currently working on a GraphQL server (using Graphene), and thankfully I'm able to not use Relay (with which it tightly integrates). So I'm able to implement my own pagination and filters.
What's the reason for posting this? It's been posted before (https://news.ycombinator.com/item?id=10667783) and the repo seems to be dead since beginning 2017 (4 open PR's from 2017).
It also looks like it doesn't fit the current web-meta anymore :)
Wha, so the exchange format is already open. So how would they ever lock everything in.
Second I feel that Microsoft will be a much better guardian than google in this respect. Google doesn't have too many OS projects, and their most valuable software is closed source, with closed formats, with little room for data-exchange...
How come we don't have proper calender sync yet, f.i.
Microsoft has in recent years been much better in their OS efforts. And they haven't killed any promising projects as opposed to G
> if there was a place to show off these cutting edge tricks? This is a competition where jugglers on the cutting edge can shine.
There's the ejc :) http://www.ejc2018.org/
But when it's a trick that only lands 1/10, will you enjoy watching them fail for a while, possibly with a lenghty setup and stay interested in it? I think it's usually the jugglers not showing them because they're not consistent yet.
Its a bit more complicated than that, since the only constraints is the yarn and physics. And there's infinite possibilities of stitching things together in intricate manners.
Then deciding whether something is nice/wanted, is in the eye of the beholder :)
Hmm, it's not great they intend to send this information to the great firewall in the sky. If it were mozilla's own servers, I'd re-enable the usage collection on nightly.
Bit more of the same with the screencapture features, it's a shame we can't host and configure our own services....
This happened in juggling as well, describing the patterns in a notation allowed people to find new ways to throw objects: www.youtube.com/watch?v=7dwgusHjA0Y
There's some caveats with this approach, since your DB has to keep track of the split state since you've started the transaction, it's quite a lot busier. So don't keep transactions open for any long stretches of time ;)
The developer edition is bit more bleeding edge than beta, but less than nightly. Nightly is updated daily. I'm not sure what the developer frequency is. But if your sporting it, you're getting the fresh features not entirely ready.
It's a shame they didn't roll a proper package manager with the language toolkit. Having your executable depend on having some lib installed is quite a pain. But how do you share libraries properly then? Especially without a proper way of bundling deps in your code...
Using cargo always makes me feel at ease when writing Rust. Haven't dabbled with linkers though.
They are different data types, but integer is also ambiguous, did you mean signed or unsigned, 32 or 64 bit.
Its about your use case, and when your parsing something with loose typing into stricter types, make sure you validate accordingly. But being able to specify the exact type kind of defeats the purpose of an interchangeable data format.
The problem with taxing income is that it taxes the lower/middle class heavier than upperclass. Usually the upperclass has ways of diverting their income into other means. Taxing profits is the current approach. There's been talk about taxing revenue for companies. Which is measurable on a nation's level