2,281 karma · joined April 18, 2011
username at gmail
As far as constantly rebuilding and deploying things, we would be doing that anyway. We do dozens of deploys a day to push new code, that means building new images every time, if one of those deploys picks up a security fix that was recently merged upstream, great.
What I find fascinating about the cyberpunk sensibility is the dramatic shift from the classical view of the future. When you dig into older science fiction it is almost universally accepted that the future will be clean, bright, and government-controlled. Sure, the spaceship crew might have to dispatch some weird bug creatures, or family's robot might have gone haywire, or Big Brother might be watching your every move, but it's taken for granted that technological progress has kept pace, rockets are zooming around, and power has been steadily accruing upward to the government, which is basically taking care of things. The biggest problem might be that the government (or should I say The Empire) has gotten a bit too much control, and some rebels have banded together for the sake of Freedom.
The cyberpunk sensibility and vision is not only darker, but significantly more subversive. Power has not conglomerated in the hands of the government, it's been usurped by corporations and wealthy individuals. Technology has not solved hunger, poverty, sickness, or human suffering, in fact in many cases it has made them worse. The environment has been fucked by centuries of industrial abuse, the cities are a mess, drugs and crime are rampant, the streets are dirty, even the rain is dirty. Technology never managed to lift mankind out of its daily struggle, humanity never banded together in search of the stars, and the hope of that clean, bright, government controlled future has become a cruel joke.
You still have not said WHY it's not a great idea, or what the benefits of defining the interfaces at point-of-use are.
> Tempe Police Chief Sylvia Moir said that from viewing videos taken from the vehicle “it’s very clear it would have been difficult to avoid this collision in any kind of mode (autonomous or human-driven) based on how she came from the shadows right into the roadway."
This seems like an unfortunate accident, but it's not at all clear that the car was at fault or that it could have done anything to prevent it. There was even a human behind the wheel and they didn't react in time either.
> The most obvious of which is that it has only one type that fulfills the interface with no obvious means of extension. (sic)
Seems obvious to me.
type Cat struct{}
func (a Cat) Speaks() string { return "meow" }
Does this not work?
> Functions typically take concrete types instead of interface types.
Ok...? This seems like some arbitrary rule that the creators of Go claimed was a good idea, I guess. The author has offered no justification for it. In general I guess I fail to see most of the proclaimed benefits of Go, every time I read articles like this I come away favoring something like Java for anything in the application layer. I can see preferring Go to C for low-level and systems programming, but I shudder to think of what a mess the large Go codebases must look like.
Historical volatility: https://bitvol.info/
https://www.perforce.com/downloads/visual-merge-tool
Example:
https://www.perforce.com/sites/default/files/image/2017-06/s...
> The system [...] has been hailed as a way to potentially save millions of dollars
Does not compute.
BitConnect is in the top 20 market cap, doesn't get much fishier than that.
Which is precisely when tree-style horizontal tabs are better. Because you can see the entire title of each window, their nesting, and easily scroll through the list.