Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
shusson
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
46 ms
·
391.
▲
by
shusson
9y ago
> Is there development timeline really that absurd though? It's not clear to me what their development timeline is, although constant Alpha releases are promising. > Editing to add that we're not even mentioning the fact tha
392.
▲
by
shusson
9y ago
How are you managing regulatory issues? The Apple watch is not a legal medical device, so my understanding is that it cannot make any diagnoses recommendations to the user.
393.
▲
by
shusson
9y ago
Your expectations are probably in line with reality, but Star Citizen does not sell itself as a casino. They entice you to spend money and promise you something great with little mention of risk. I really hope they create a great game, but
394.
▲
by
shusson
9y ago
Thanks, because of your comment I'll take a second look.
395.
▲
by
shusson
9y ago
The two biggest issues I see are: - Requires complete access to all the data you type - They don't own any platforms, and the product is potentially a core feature of a platform/service. For example if Google decides to roll their
396.
▲
by
shusson
9y ago
I'd add a section/row on `browser vulnerability: XSS`.
397.
▲
by
shusson
9y ago
My understanding is that the distributed[1] capability of MapD is not open sourced. And I'm guessing a lot of the companies (especially the ones with money to burn) that would use MapD require at least some horizontal scaling. [1] http
398.
▲
by
shusson
9y ago
Has anyone read any papers about the relationship between code coverage and defects?
399.
▲
by
shusson
9y ago
What about Android or iOS?
400.
▲
by
shusson
9y ago
Any chance SQream DB will be open sourced or a demo version? It seems every Column based GPU DB I find is behind a paywall and targeting enterprise levels.
401.
▲
by
shusson
9y ago
Why spend resources developing AI for a plane designed for Humans? I'd imagine that AI on cheap drones/missiles vs traditional human fighters would be a more interesting simulation.
402.
▲
by
shusson
9y ago
> Test more than you think you should I think this is a dangerous way of thinking. Writing more tests does not necessarily improve code quality or decrease the risk of defects. A focus on coverage can lead to bloated tests which end up t
403.
▲
by
shusson
9y ago
> In duck-typed like Ruby/Python, you don't necessarily know whether a piece of code is going to fail, so you assume it does You should always assume there may be runtime errors regardless of whether you have some sort of stati
404.
▲
by
shusson
9y ago
I love the concept, but I think the added complexity is hard to trust, at least for now.