Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
mbell
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
52 ms
·
451.
▲
by
mbell
11y ago
> Who is supposed to teach people what code is? 'But no one told me I needed to know this' stops being an excuse as of adulthood, if not earlier. Anyone who cares what coding is only needs curiosity and an internet connection,
452.
▲
by
mbell
11y ago
Any data on the SDE of the new display? I'm really excited about VR, have a DK2 and am really impressed with the experiences available already. But, I've found it very hard to use for long periods of time (more than 20-30 minutes)
453.
▲
by
mbell
11y ago
> Apple does a lot of work in hardware and hardware manufacturing, both areas which are pretty capital-intensive and might not lead themselves as easily to the startup world. There is some truth to that but it's not the custom chip
454.
▲
by
mbell
11y ago
> As for "done before", a core feature of Cockroach is true ACID transaction support, including snapshot isolation, something no distributed NoSQL database I know about supports. Zookeeper has ACID transactions which I believe
455.
▲
by
mbell
11y ago
> Cockroach is a distributed key:value datastore (SQL and structured data layers of cockroach have yet to be defined) - emphasis mine I guess this is interesting, but distributed hard consistency pure K-V stores have been done before
456.
▲
by
mbell
11y ago
This is not correct. The vulnerability is in `bson-ruby`[1] which is written by MongoDB and used by Moped (and thus Mongoid), the official Ruby driver from MongoDB, and Mongo Mapper. The only thing that _isn't_ vulnerable is Moped'
457.
▲
by
mbell
11y ago
The JS implementation is really cool and very smooth. The request to art.com's search API which is taking many seconds and probably isn't making their servers very happy, is not so cool, and possibly illegal.
458.
▲
by
mbell
11y ago
> Partly because we had no unit tests (a whole 'nother discussion) I think that the is the primary point. If you have good test coverage at each level, it's actually really easy to make large sweeping changes to a codebase. If
459.
▲
by
mbell
11y ago
For those looking for a high performance inter-thread library, I've found LMAX's disruptor library has worked quite well: https://lmax-exchange.github.io/disruptor/
460.
▲
by
mbell
11y ago
Pretty empty article TBH. This is not only standard, but very simple pick and place assembly that any CM can do. Most of what goes into 'Making an SSD' is the ASIC and firmware design on the controller. The actual assembly is incr
461.
▲
by
mbell
11y ago
I don't think that solution is viable within the constraints the parent post is talking about. There are many problems that come up with millions of users. Proper load balancing in that case is not simple and mostly dependent on the bu
462.
▲
by
mbell
12y ago
Any time you have per user data you have an a clear shard key. i.e. instead of one Redis instance you have 100 where each serves a subset of users. In practice sharding isn't quite so simple but having a clear boundary makes it fairly
463.
▲
by
mbell
12y ago
I agree it's what the 'next economy' will look like, but it's also what the 'last economy' looked like. Prior to the entire tech movement was agriculture, resource harvesting and material manufacturing. Previou
464.
▲
by
mbell
12y ago
LXC isn't a 'feature of the linux kernel' it's a user land library that uses a set of linux kernel features (e.g. cgroups, namespaces, etc) to expose an api for creating system containers. LXC isn't part of the kern
465.
▲
by
mbell
12y ago
This is what the SpaceX barge uses: https://www.thrustmaster.net/out-drive-propulsion-unit/porta...
466.
▲
by
mbell
12y ago
> people who want to use Linux-technology, like Docker What defines Docker as 'linux technology'? It has an execution driver API specifically designed to support multiple backends, e.g. BSD jails. I wouldn't use the fact t
467.
▲
by
mbell
12y ago
The error codes nor the transport are important here. You can make an arbitrary number of requests that can respond with various responses (or fail) in arbitrary order. Who do you listen to? Which response is 'correct'? Sure you c
468.
▲
by
mbell
12y ago
This has nothing to do with REST, the same issues exist.
469.
▲
by
mbell
12y ago
If there is no throttling, there could be a dozen requests, with different responses arriving in arbitrary order. Which one do you believe to determine the outcome of the operation? How long do you wait for responses? etc. etc. If your goin
470.
▲
by
mbell
12y ago
That doesn't make the situation any better. Request 1 takes the 'token' Request 2 sees the token gone, returns 'silent success' Request 2 response reaches client, client assumes success. Request 1 fails somewhere in
471.
▲
by
mbell
12y ago
This just moves the concurrency issue to the client, particularly for xhr requests. Say you double click on some action with a one time token, the first request gets to the server and succeeds while the second request fails due to the token
472.
▲
by
mbell
12y ago
There is nothing special about the barge stabilization, it's off the shelf marine tech. A few azimuth thrusters controlled by a station keeping system. The only unusual thing about it is that the azimuth thrusters are a lot more powerf
473.
▲
by
mbell
12y ago
I don't think there will be meaningful slowdown from taking a 'good developer' with a lot of experience in Rails and throwing them into Django development. It takes very little time to figure out the proper way to do somethin
474.
▲
by
mbell
12y ago
Command to learn: - git rebase (if you learn everything you can do with this command, you'll pretty much know git inside and out) Other useful stuff: - git diff - git diff --cached - git log --graph --decorate --pretty=oneline --abbrev
475.
▲
by
mbell
12y ago
> Most APIs seems to respond within 20 to 200ms. Many of our internal services respond in < 5ms while handling thousands of requests per second. 1ms of routing a big deal.
476.
▲
by
mbell
12y ago
You don't have to use a JS MVC framework just because you built your core logic behind a JSON API. You can just as easily have a server side rendering app talk to the JSON API instead of the directly to the datastores. You get to stick
477.
▲
by
mbell
12y ago
> I also wonder whether it is worth it? Are all developers really blocked when the build fails? In our setup building the deployment artifacts is contingent on tests passing so if the build isn't passing, no one can deploy.
478.
▲
by
mbell
12y ago
JavaEE has some truly terrible specs in it, particularly JSF and CDI. I also haven't seen a great deal of cohesiveness in the platform, e.g. when EE6 was released JSF's injection system only partially supported CDI (ViewScope for
479.
▲
by
mbell
12y ago
> Sorting algorithms like merge sort are a basic example. Using recursion for those is fine. General sorting is exactly the type of thing I never use recursion for. Merge sort is O(n log n), sorting 100M records with a recursive implem
480.
▲
by
mbell
12y ago
> 5. Difficulty seeing through recursion It may be a function of the code I work on but I generally avoid recursion unless I'm really sure about the bounds of my input, which is rare. Few other things can take a smoothly operating
More ›