Hacker Newsnew | past | comments | ask | show | jobs | submit | more BiteCode_dev's commentslogin

Antifragile, at least by the definition of Taleb that I believed coined the term, is not "bouncing back quickly", but actually improving after the event.

I don't see how a computing system could be anti-fragile. A team building one, certainly, learning from each mistake and improving the system.

But a system by itself, baring some miraculous learning AI, I don't see how.


An anti fragile computing system is a deep learning algorithm because it gets better from fluctuations in data as it forced it to generalise than end up in local minima


Not to mention:

- super hard to cache if any client can basically generate an infinite number of different queries.

- which dialect of SQL ? If you change DB or upgrade version, do your ask all clients to change as well ?

- how do you do query that involves several data sources ? Some response data come from redis + elastic search + postgres. That's why FB created graphql. That's also why it's so limited in scope, so that complexity is manageable.

- do you want to expose clients to implementation details such as OUTER JOIN vs INNER JOIN vs an array ? Or let them figure out tricky queries involving HAVING, DISTINCT, COUNT or subqueries ?


> do you want to expose clients to implementation details such as OUTER JOIN vs INNER JOIN vs an array ? Or let them figure out tricky queries involving HAVING, DISTINCT, COUNT or subqueries ?

No, you implement an exposed schema for each app (or possibly more granular) that consists of objects (mostly views, possibly sprocs) optimized for the planned access pattern of the app (or whatever client/component thr schema is for), including convenience views abstracting those things away to the extent appropriate for the use case. That’s been a widely known RDBMS best practice for decades.


Direct SQL from the client definitely isn't for everyone, but these problems aren't insurmountable.

Caching: This is true of any API allowing, for example, advanced search. If you can get by without it, great, but it's often a requirement.

Dialect: I don't think it's a terrible idea to bet on one (ideally stable and FLOSS) database, it's just a risk to be managed, and I think it can provide benefits in some cases. Or you could be fancy and use jOOQ's SQL dialect translator (this could also be used to create a "custom dialect" without some features).

Multiple data sources: You could use PostgreSQL's Foreign Data Wrappers. An unorthodox solution, but it allows seamless access with fast joins.

Complex SQL features: I don't think it's really a problem, in complex analytics code I think some users would actually appreciate having all these features. It can be a code quality challenge, but I think that's better solved on a personal level.

This approach does have real problems, like it being hard to prevent DoS attacks, but I don't think there are as many problems as it seems on first glance.


Then you need to keep the update server alive for a long time.


Or make the update available for download to install via usb drive.


Is that something that can be done now, or would that too require a firmware update to introduce that feature?



Most things in programming are human conventions that you have to learn. There is rarely a way to guess or figure things out. Keywords, scoping, byte order... It's all arbitrary, understanding the English meaning of the world "yield" in English will do little to help you understand generators.

No, the real problem is the reading material. If you need to debug/read doc/google stuff, anything worth something (except a few exceptions like samemax.com and so on) will be in English.

I've seen French professionals being perfectly capable programmers, but because their English sucked, their struggled to solve some problems that were a Stackoverflow post away.


I'm still using unity because it was the last usable polished out of the box usable DE for me. I'm glad they try to do this, the linux desktop needs a contender to the too rich kde and too limited gnome, but with a modern touch.


That's what tests are for.


We keep assuming body and mind are separated things, but separating the concept of ink and paper doesn't help you understand the full nature of a book.


Do you have a link to a tutotial for that ?


No, but it's very easy to grasp. https://blog.cloudflare.com/tls-session-resumption-full-spee... did it perfectly.

Basically, you need to get the session ticket from the webserver being available at the backend, and set its lifetime to something reasonable.

At least NGINX can then handle all of the session resume/renew logic by itself.


At first it was hard to read for me, but then I realized that in their design, the code always flowed from left to right, starting with the data you want to work on (or the data producer).

So it's always: data => process => process => process.

Left to right, no surprise, always the same thing first.

I kinda like the idea, although it's weird to get used to due to unfamiliarity.


PWA are crippled on apple phones.


That's not a surprise because it would make a dent into Apple's profits but did he need a PWA for picking a movie to watch? Share a URL to friends or place a QR code in the living room and that's it.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: