jpcapdevila

Haha, most code evolve into crap. But crap can solve real user & business needs.

I was having this conversation two days ago. I believe free will is an illusion, everything is ruled by causality beyond our comprehension.

But even as I say write it, in a couple of minutes my brain will jump back into thinking I'm in control. It's very strange.

Singapore!

I spent a week there 7 years ago and I loved it.

The city was cool and modern, yet clean and civilized.

I was born in Mexico city, currently living in salt lake city Utah. I think living in Asia for a while would help me grow and expand my perception of the world.

For me full stack means someone that can deliver a complete product (ui, server side business logic, database, deployment) on its own.

Makes sense and I agree. For simple things I still do vanilla js. As soon as I need to re-use components or shared state between pages I go with sveltekit.

Very nice trip down memory lane! My experience was very similar.

For me the next step, the fifth era if you will, is javascript that manages the persisted distributed state for you without any backend or db specific API.

You push something into an array and it is magically there for another user in the other side of the world.

I'm working on something like that: https://javascriptdb.com

Maybe you will like https://svelte.dev/, I find it more close to good old html. For example, a component that is not interactive is basically an html file with an <style> tag and some html markup.

Thanks Ben. I appreciate the feedback, I will add vanilla samples but also samples for each framework, including SSR.

The DB access works fine on both places, I use it from svelte kit load function without problems. I haven't played with authenticated SSR, I'll make sure to include that in the samples.

Both firebase and appwrite are amazing platforms. I use firebase extensively at work, it works great and it scales.

The main problem with firebase is that you can't self host it, this means you can't easily test or replicate environments.

The emulators are limited: indexes are not enforced, copying the production database (no more than 50k documents) to my macbook pro crashes the emulator.

Also the DSL used to define security rules is not flexible enough. I've seen developers skip defining rules because they don't get it to work.

Appwrite is great and you can self host it, but it introduces concepts/APIs to query data and secure it that you have to learn. They also try to solve the problem for all platforms and languages.

JSDB tries to extremely simplify things and just use plain javascript for everything.

You should use JSDB if you love javascript.

That being said, firebase & appwrite are both production ready and JSDB is not there (yet!!)

Sure. You can host it yourself for commercial purposes and you don't have to open source anything in your product, just like you can with MIT. The only difference is that if you want to create a service that offers JSDB as a service (compete with javascriptdb.com) you have to open source it. The idea is to make big cloud companies contribute back.

Thank you. Out of curiosity, what language do you usually use to develop your backend?

Agreed, there are fun technical challenges to tackle. I think the project will eventually take a compiler approach.

At least that's the plan to enable indexes. Parse callback functions passed to .filter and convert that into native DB queries.

Thanks for the feedback. I'll add the supported engines to the package.json

About ES modules, I decided to start with esm because it looks like everything is moving in that direction. That being said I will support both cjs and esm soon.

@ben Same as the other commenter, I'm currently using it without problems. I configured max instances to 1 and that seems to be working fine. What am I missing?

Super excited about this one. We've been struggling with deployment times and timeouts for long running tasks.

The function versioning seems interesting for rollouts.

It's for background running tasks. In my company we have functions that process tons of medical records. We call this HTTP function from a cloud task queue, the previous 9 min limit was annoying.

This will make our team happy.

When I go to any page under cloud.google.com I get "Service Unavailable". This is from Utah, US.

Edit: I only get this error on docs etc, console works fine.

Yes, I have launched a couple of svelte (sapper) over the last two years. No regrets so far.

What they are rewriting is sapper, the next-like framework. It's probably subjective, but I think the ergonomics and low code/noise ratio worth the immature state.

Also my team loves it, JR engineers find it easy to learn, even our designer likes to contribute now that we are using svelte.

Firebase + svelte.

Firebase gives you auth, serverless database that you access from the client directly, storage etc.

Svelte gives you low overhead, easy to write and easy state management components. it's very close to plain HTML & JS.

I believe he was referring to Tesla solar roof for houses.

https://www.tesla.com/solarroof

I'm currently in the US using a TN visa. I know many people with that visa, 0 rejection rate if you present the proper documentation.

Pm me if have more questions.

Yes I did! I thought I was alone. I love when movies do their best to have some sense on the tech side, it could have been an annoying "sending ransom note.." loader instead.

I use Discord daily as the main communication tool for a remote dev team. We have a voice and text channel for each project and works great.

Yes you can. You could create an smart contract where you lock X amount of eth, and set up how much the other party can withdraw each month. Then is up to the provider of the service to withdraw the amount each month, which seems to me less an issue since they want to get paid.

I think a better term would be "Dapp starter"

GPS does not work indoors, and I think all the physical web stuff is great for app discovery

Nice to hear about your experience with meteor

Take a look at Loopback, it is built on top of express, allows for rapid development and in my experience scales really good. For example it has load balancing out of the box.

It is definitely my tool when building nodejs Rest APIs