Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
themihai
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
59 ms
·
631.
▲
by
themihai
10y ago
I can't speak for the collective. As far as I'm concerned the current offers of BaaS are dead on arrival. Time will tell. I could see some value in the iPhone but I don't see much value in the current BaaS offers. Not enough
632.
▲
by
themihai
10y ago
Eventually wasm will provide GC. Edit: It's on the roadmap just after MVP so I wouldn't say it's that far. Also based on the latest talks from Luke at City Hall(I can't find the link) the access to DOM could arrive even
633.
▲
by
themihai
10y ago
yeah but there was no stable Perl 6 in 2012. Perhaps `dead on arrival` would have been better said than `too late`.
634.
▲
by
themihai
10y ago
I didn't say the technology is DOA. Just the current offers which seem locked in to specific vendor implementations. The current BaaS offers are too intrusive and just not good enough to worth the switch from a PaaS to a BaaS.
635.
▲
by
themihai
10y ago
Maybe worry free if you don't need to look under the hood. If the manufacturer would lock the hood you would never know :)
636.
▲
by
themihai
10y ago
I think it's basically a stateless PaaS/microservice with a set of constrains/APIs on top. The BaaS/Serveless architectures also seem to have their own sub-categories based on the constrains/target. Some are fat(i.e
637.
▲
by
themihai
10y ago
Well if I can't use it now due the constrains mentioned above it is dead to me. Would you bet your project on Google functions[0]? [0] https://cloud.google.com/functions/docs/
638.
▲
by
themihai
10y ago
Well that's my point! In this particular case(BaaS) the current implementation is not worth it due the lock in. The issue with the lock in is that you can't fix it yourself if it's broken. Maybe if it would be free and my pr
639.
▲
by
themihai
10y ago
I actually think the opposite. Serverless architectures are the future for most of the app servers that need a language agnostic API. Maybe I didn't get it right but to me BaaS is just a PaaS with a common API interface(i.e. authentica
640.
▲
by
themihai
10y ago
Well they are. I've always asked myself why there is no such service..then it was GAE and then docker and here we are!
641.
▲
by
themihai
10y ago
I don't follow. You can write other modules in different languages. The data sources are language agnostic. Nobody forces you to do use a specific programming language in the first place unless the platform is close sourced. The point
642.
▲
by
themihai
10y ago
RethinkDB doesn't seem to be a general purpose BaaS. I definitely don't think BaaS is a bad thing. It's just that the current flavours are not worth it. They are mostly some kind of MVPs. Edit: I'm not very familiar wit
643.
▲
by
themihai
10y ago
JS as target will always be slower and bigger(as payload) than WASM as target so my point is that JS as compilation target is no longer relevant once WASM is supported(i.e. most likely by the end of the year). It makes little sense to start
644.
▲
by
themihai
10y ago
Well, the point is that the benefits don't outweigh the drawbacks because of the vendor lock-in. Whenever you hit a limitation there is NOTHING you can do. No duct tape! Also on long term the vendor roadmap may not align with your busi
645.
▲
by
themihai
10y ago
The vendor lock-in alone is enough to make BaaS dead on arrival. Some seem to lock you not only on specific platform APIs but also on a single programming language(i.e. javascript) like it wasn't worse enough to have a single language
646.
▲
by
themihai
10y ago
Isn't quite late for a JS backend given that we have WASM now?
647.
▲
by
themihai
10y ago
Well that's exactly what I need: A format that communicates structured data, friendly with GET requests and backward compatible with query string encoding. Why there is no such format/standard yet? Is it that unusual?
648.
▲
by
themihai
10y ago
I've started doing just that but I have a micro-services architecture so I need to implement the custom encoding schema on multiple stacks (i.e. java, python, go) which takes time. Being non-standard the external consumers will have to
649.
▲
by
themihai
10y ago
I don't think it's search because the server must provide a response for each resource or an error. If one resource is missing the server should return an error. --- Concerning the post I would move it to `ask HN` but I don'
650.
▲
Don't use GET for APIs
2 points
by
themihai
10y ago
|
12 comments
651.
▲
by
themihai
10y ago
The demo link doesn't work
652.
▲
by
themihai
10y ago
That's understandable. I've just tried to prove the point that Rust is still a language in flux compared with Go, hopefully making the Rust team aware why some developers hesitate to use Rust on new projects.
653.
▲
by
themihai
10y ago
Unlike the Go spec that's prose only. Why is it not accurate? Does the language change that often?
654.
▲
by
themihai
10y ago
What's the equivalent of this[0] in Rust? [0] https://golang.org/ref/spec
655.
▲
by
themihai
10y ago
Testing nightly makes sense. >>What if I would like to guarantee this property for my own code? I think that should be an exception if the backward compatibility is to be trusted.
656.
▲
by
themihai
10y ago
I would like the code developed now to work with all subsequent rust releases until 2.0 so that I can take advantage of improvements to the compiler and std libraries without any additional effort. A small effort may effort may be require
657.
▲
by
themihai
10y ago
Does Rust have a formal specification?
658.
▲
by
themihai
10y ago
You are right about the compiler changes but even so you can't compare 1-2 compiler BK with Rust which has language changes as well. Compiler changes are the norm in Rust. >> The parts of the Rust standard library that are marked
659.
▲
by
themihai
10y ago
Well, that's my point! You shouldn't need to test various versions of Rust if you there is a strong backward compatibility policy. I might be mistaken but my feeling is that most of the rust devs are using the nightly version thus
660.
▲
by
themihai
10y ago
I'm sorry to say but you must be delusional. Can you list the these `aggressive` breaking changes? There were only 7 releases since go1 and I fail to find any breaking change in the language specification. On the other side each Rust r
More ›