daliwali

15 ms·

91.
by daliwali 9y ago
This may be a stupid question but I glanced over the marketing website and didn't really understand how logs are stored. - Are you storing each log event as a row in Postgres? - How do you rotate logs, what happens when logs get indefi
92.
by daliwali 9y ago
I have a rather unpopular opinion that JS libraries get popular for reasons unrelated to merit, such as corporate backing (React), appeal to beginners (jQuery), and adding syntax sugar that has no value to end-users (Underscore/Lodash,
93.
The Business Model of SpaceX Is Quintessentially American Fraud(dissention.wordpress.com)
7 points by daliwali 9y ago|12 comments
94.
by daliwali 9y ago
This is expected in some fields such as embedded programming, it's reasonable to look at source code just to figure out how hardware works. Or web front-end where you shouldn't be sending huge payloads to the browser anyways. You
95.
by daliwali 9y ago
I'd settle for consistent, predictable, and cheap. Generic doesn't matter if it solves my specific problem and ubiquity is a social problem. Enterprise pays a lot for bespoke solutions as well. A very good reason to write your own
96.
by daliwali 9y ago
The point was more about popularity having no correlation with anything else. There is tons of unpopular code that is really, really good, these are hidden gems. Likewise, there is popular code that is quite bad or mediocre regardless of nu
97.
by daliwali 9y ago
Popularity is not an indicator of anything other than popularity. McDonalds is the most popular burger sold in the world, that does not make it good. Length is an important consideration and most never consider it, partly why software is no
98.
by daliwali 9y ago
Here's an overlooked one: your dependencies. Every programmer should read the (presumably open source) code they depend on, but almost nobody does it. Some look at documentation, but not everyone even does that. What you may find is th
99.
by daliwali 9y ago
A practical benefit for using JSON-LD in API development is being able to link every field in the response directly to a definition, ideally a shared one such as schema.org. This overlaps a bit with definition formats like OpenAPI (Swagger)
100.
by daliwali 9y ago
Nobody has brought this up: why should we trust proprietary software running on the vendor's server? And more practically, how can we expect this service to be reliable in the future (related: Parse shutdown). I think this is a disturb
101.
by daliwali 9y ago
The biggest anti-pattern of all: marketing your API as RESTful, when it is really more RPC-like. I agree on all points of this article. The only nitpick I have is that tunneling through GET/POST is strictly necessary for HTML forms, si
102.
by daliwali 9y ago
REST actually has nothing to do with HTTP. It happens to map nicely to HTTP, but what it really is, is a set of architectural constraints.
103.
by daliwali 9y ago
I double checked my codebase and it looks like it's just JSONB, which CockroachDB also doesn't support [0]. Sorry to bother about missing features, but there are really some things that prevent a smooth transition from Postgres. [
104.
by daliwali 9y ago
CockroachDB looks like a great alternative to PostgreSQL, congrats to the team for doing so much in such a short time. The wire protocol is compatible with Postgres, which allows re-using battle-tested Postgres clients. However it's a
105.
by daliwali 9y ago
I think abstract, non-empirical knowledge can be useful. For example, all of mathematics. It is unreasonably effective at modeling nature, there is no reason why nature must adhere to abstract mathematics. For example the invention of the i
106.
by daliwali 9y ago
A variation of this already exists, called the Cognitive-Theoretic Model of the Universe (CTMU) [0]. It is dismissed by critics as not being based on empirical methods or pure reason, which is what it's getting at: science isn't t
107.
by daliwali 9y ago
I hold a degree in mathematics. Small-minded HR drones have told me I'm not qualified to do programming since I'm not formally trained in computer science. I have been doing this since I was a kid. Don't listen to them. Every
108.
by daliwali 9y ago
I was interested in learning Rust as a safer alternative to C a few years back, and have been observing its progress from afar. I'm much less optimistic about it now, though I only have a layman's understanding of it. The language
109.
by daliwali 9y ago
Every single one of those websites use HTML, a common media type, with semantics defined in that standard. What's missing are the application-level semantics like what's a "flight search" and "flight booking",
110.
by daliwali 9y ago
APIs defined in XMLRPC, CORBA, SOAP, et al, can have clients and servers implemented by anybody. Programmers don't seem to learn from history and struggle with thinking over time. These formats worked well in a time when a single party
111.
by daliwali 9y ago
A good rule of thumb is that if a REST API has an SDK, then it's not really RESTful in the first place. SDKs are an enormous effort to create and maintain for every HTTP API, I think it's a malpractice that is all too common. Brow
112.
by daliwali 9y ago
Actually gRPC is about the same as other HTTP based APIs, it is just a more efficient RPC. All of them are lacking what made the web scalable in the first place. - HTTP APIs are worse than websites of the 90s. At least a browser could be ex
113.
by daliwali 9y ago
I made a small mistake in the first point, got downvoted to oblivion and people seemed to stop reading there: the binary serialization indeed has backwards and forwards compatibility. However, the textual serialization lacks this compatibil
114.
by daliwali 9y ago
RPC has its own set of limitations, which if your application qualifies, might be a good fit: * Coupled server and client. gRPC uses protocol buffers which have zero backwards compatibility. * Zero discoverability. The client knows in advan
115.
by daliwali 9y ago
Most servers don't need to handle anywhere close to Google traffic and some downtime is acceptable -- the network is more unreliable. Sacrificing 0.001% uptime and "scalability" (whatever that means) is worth it.
116.
by daliwali 9y ago
Many important concepts start as unknown, and then once explained in great detail, seem plainly obvious. It took a lot of reasoning to convince people that in fact zero is a number (but zero doesn't exist!) and now it's taken for
117.
by daliwali 9y ago
>...until employers start asking you to work on every buzzword of the month. This is absurd. Do you do everything your boss tells you to? It's incredible that some employers survive long enough to chase the next fads, which only pro
118.
by daliwali 9y ago
I think all of this serves to highlight how valuable information technology is right now. People can get away with massive inefficiencies, producing tons of garbage code, not-invented-here habits, horrible performance, and still run a profi
119.
by daliwali 10y ago
More sophisticated ways to reject connections rely on heuristics and may result in denying legitimate requests. I don't have all the answers, I'm just suggesting a way that doesn't consider all requests equal. Every CORS pre-
120.
by daliwali 10y ago
One could limit concurrent connections per address. The idea is that an OPTIONS request which doesn't take much resources at all could be treated with a different weight than a POST which costs the server time to process.

More ›