!warning could be longer.
I must something let go:
Im now 24 ,my life was not easy .
I got bullied all the time in school from 1 to 10 degree. I had a dream since i was 6:"no i dont wanna be a police man, fire fighter, astronaut....i want to be a programmer "..
My father did me to make an apprenticeship with Volkswagen after i finished my "middle school" (10th class);
2 years of mobbing and be sad i leaved that motherfucking "-aship"
After a while my father again wanted to ,i must to an "-aship" .yeah hes been right, but i dont want to do and work like you do!!!.. then again after "fighting" my dad (parents), i was reliant to social help for a year..
(U must know,my dream was always in my mind)
I met a girl in a different federal state in germany and moved up to her.
I worked as a daywage man to get us money.
1 year was over and then i found out the apprenticeship as web and mobile developer (computer scientist) . I applied for this an got a place.
Now my fucking dream comes true in a few months!
Just wanna say that you never should give up your interests or dreams, doesnt matter how old you are!!!!
My journey begins 2017 and yours?:))))

Shit that annoys me: People use the store (insert google play/apple/other) rating with one star to ask questions instead of fucking filling the stupid contact form or send an email to tech support.

Curious did any of you have a specific reason to learn how to program?

I wanted to be involved in aerospace but realised I'd probably never be an Astronaut, but i could learn how to write the software that controls the spacecrafts!

A year ago I built my first todo, not from a tutorial, but using basic libraries and nw.js, and doing basic dom manipulations.

It had drag n drop, icons, and basic saving and loading. And I was satisfied.

Since then I've been working odd jobs.

And today I've decided to stretch out a bit, and build a basic airtable clone, because I think I can.
And also because I hate anything without an offline option.

First thing I realized was I wasn't about to duplicate all the features of a spreadsheet from scratch. I'd need a base to work from.

I spent about an hour looking.
Core features needed would be trivial serialization or saving/loading.

Proper event support for when a cell, row, or column changed, or was selected. Necessary for triggering validation and serialization/saving.

Custom column types.

Embedding html in cells.

Reorderable columns

Optional but nice to have:

Changeable column width and row height.

Drag and drop on rows and columns.

Right click menu support out of the box.

After that hour I had a few I wanted to test.

And started looking at frameworks to support the SPA aspects.

Both mithril and riot have minimal router support. But theres also a ton of other leightweight frameworks and libraries worthy of prototyping in, solid, marko, svelte, etc.
I didn't want to futz with lots of overhead, babeling/gulping/grunting/webpacking or any complex configuration-over-convention.

Didn't care for dom vs shadow dom. Its a prototype not a startup.

And I didn't care to do it the "right way". Learning curve here was antithesis to experimenting. I was trying to get away from plugin, configuration-over-convention, astronaut architecture, monolithic frameworks, the works.

Could I import the library without five dozen dependancies and learning four different tools before getting to hello world?
"But if you know IJK then its quick to get started!", except I don't, so it won't. I didn't want that.

Could I get cheap component-oriented designs?

Was I managing complex state embedded in a monolith that took over the entire layout and conventions of my code, like the world balanced on the back of a turtle?

Did it obscure the dom and state, and the standard way of doing things or *compliment* those?

As for validation, theres a number of vanilla libraries, one of which treats validation similar to unit testing, which seems kinda novel.

For presentation and backend I could do NW.JS, which would remove some of the complications, by putting everything in one script. Or if I wanted to make it a web backend, and avoid writing it in something that ran like a potato strapped to a nuclear rocket (visual studio), I could skip TS and go with python and quart, an async variation of flask.
This has the advantage that using something thats *not* JS, namely python, for interacting with a proper database, and would allow self-hosting or putting it online so people can share data and access in real time with others.

And because I'm horrible, and do things the wrong way for convenience, I could use tailwind.
Because it pisses people off.

How easy (or hard) would it be to recreate a basic functional clone of the core of airtable?

I don't know, but I have feeling I'm going to find out!