jcormont

6 ms·

1.
by jcormont 7y ago
Hey everyone, in this article I explain how Typescene works using a simple, practical example. I also go through some of the differences with other frameworks.
2.
Typescene Framework: Quick Start(medium.com)
1 points by jcormont 7y ago|1 comments
3.
by jcormont 7y ago
Bingo
4.
by jcormont 7y ago
Just read it like natural language. Where it says UIButton.with({ label: "OK" }), that's a Button With a Label of OK. Editors with TypeScript-aware autocomplete (e.g. VS Code) will suggest most of the identifiers here, and te
5.
by jcormont 7y ago
I guess a good rule of thumb would be if you don't see the benefit of using a framework for your project, you probably don't need a framework in the first place :)
6.
by jcormont 7y ago
Yup no worries, I work with my own standard contract and work like this is excluded. Valid point though, thanks.
7.
by jcormont 7y ago
Not quite, but maybe close enough: https://typescene.dev/docs/guides/first
8.
by jcormont 7y ago
Not the content itself. There's no need, it's generated by GitHub pages and works fine (and no issues with SEO). The search popup is implemented using Typescene though.
9.
by jcormont 7y ago
I've mostly made this for use with my actual (paid) project work, so the idea was I 'might as well share'. Turned out to be much more work than I anticipated :) Definitely not a hobby project though, I'm hoping eventuall
10.
by jcormont 7y ago
Yes, for the View part. There are also other components that handle logic and your data model. Writing 'new Button' for every single UI component would be really cumbersome, that's why there's also a 'template'
11.
by jcormont 7y ago
The onClick event handler refers to a method on an object that exists when the component is rendered , not when the template is parsed by the JS interpreter. So, to refer to the method itself you'd need to do something crazy like go t
12.
by jcormont 7y ago
Totally understand how this could rub someone the wrong way, but my intention here is mostly to clarify my own thought process. Not so much "everyone else's shit stinks but mine smells like roses", but rather "my own shi
13.
by jcormont 7y ago
Not saying that HTML isn't also readable (although... once the number of attributes grows larger I always end up with a bit of a mess, but that might just be me). The real feat here is getting rid of the hacky way that XML and/o
14.
by jcormont 7y ago
I do mostly non public work, LoB apps in particular.
15.
by jcormont 7y ago
Examples?
16.
by jcormont 7y ago
Agreed, might have rushed this part of the intro. Edited the story to add some more important goals. Thanks for your feedback!
17.
by jcormont 7y ago
Thanks for sharing your views. The way templates are implemented is definitely a matter of personal preference, I personally don't like mixing two different languages, always seemed like kind of a hack to me. With this restriction Type
18.
by jcormont 7y ago
Sure this is a major restriction but there are lots of systems out there with architectures that never changed. I think accepting major changes from framework authors is something we learnt over time, from projects with lots of people who h
19.
I’ve spent five years writing a JavaScript framework(medium.com)
257 points by jcormont 7y ago|116 comments
20.
by jcormont 7y ago
huh? It's hosted on GitHub pages, not sure why this would happen?
21.
by jcormont 7y ago
I've spent 5 years working on a JavaScript framework. Finally sharing it with the world! Different philosophy altogether from React and Vue, those are awesome too but Typescene is built with a different purpose — please read the websit
22.
Show HN: Typescene, no-nonsense strongly typed JavaScript framework(typescene.dev)
5 points by jcormont 7y ago|3 comments