You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Simple minimal prototype of isomorphic application #115
Once we have such application we can experiment with it on different infrastructures.
Please, create a separate branch in the LogList git repo and replace everything in it with the prototype. In the future we will make more LogList related changes to the prototype and eventually when it's ready we will merge everything into master.
According to the architecture diagram in #78 the prototype will consist of two projects: one for frontend with catberry and TypeScript, and another one for backend with finch, database and other backend stuff.
For this prototype I'll place both projects in one repo. But I'm not sure if it is right in general. Maybe in the future we are going to reconsider that.
I was thinking about that too and I agree with you. We could prototype both projects in one repository, but in future we should separate them (that also means that we should compile and test them separately and I think that is the right thing to do).
@rexim, I had discussion with @pragmadash regarding using TypeScript with Catberry and currently I think that you should take a timeout at this problem. This is a separate task and I'll try to create some minimal implementation myself.
Um, guise? Isomorphic apps are kinda more complicated than that.
First and foremost, there's no magic in catberry that somehow will make your app isomorphic. It still needs something to run server-side JS. And by something I mean node.js. Can't circumvent that. (Well, you can mikel your own server-side js thingamabob, but still...)
Second, nobody -- and I meannobody needs isomorphism "just 'cause, y'know". Please refer to this fine article for the elaboration of the point. Do not go full frontal hipster, please. You need iso when time-to-presentation actually becomes a bottleneck in your conversion funnel. FFS, we do not even need to measure any conversion -- it's not like we are monetizing LogList in any way, shape or form. So, transition to isomorphic SPA will only complicate things for the devs without producing any value whatsoever.
And third -- writing isomorphic apps is not problem-solving hard. It's complicated, yes -- because there's a lot of mundane and boring stuff to take care of. So, not an achievement. A second-to-last bullet point in your CV, maybe.
Stay frosty. And never, ever, cut a deal with a dragon.
Activity
rexim commentedon May 6, 2015
According to the architecture diagram in #78 the prototype will consist of two projects: one for frontend with catberry and TypeScript, and another one for backend with finch, database and other backend stuff.
For this prototype I'll place both projects in one repo. But I'm not sure if it is right in general. Maybe in the future we are going to reconsider that.
ForNeVeR commentedon May 6, 2015
I was thinking about that too and I agree with you. We could prototype both projects in one repository, but in future we should separate them (that also means that we should compile and test them separately and I think that is the right thing to do).
ForNeVeR commentedon May 22, 2015
@rexim, I had discussion with @pragmadash regarding using TypeScript with Catberry and currently I think that you should take a timeout at this problem. This is a separate task and I'll try to create some minimal implementation myself.
rexim commentedon May 22, 2015
@ForNeVeR ok, sure. Should I reassign this issue on you?
rexim commentedon May 22, 2015
Or maybe we should create a new one specifically for TypeScript with Catberry?
ForNeVeR commentedon May 22, 2015
Agreed. Created #117. You can proceed with the server implementation here.
hagane commentedon Aug 19, 2016
Um, guise? Isomorphic apps are kinda more complicated than that.
First and foremost, there's no magic in catberry that somehow will make your app isomorphic. It still needs something to run server-side JS. And by something I mean node.js. Can't circumvent that. (Well, you can mikel your own server-side js thingamabob, but still...)
Second, nobody -- and I mean nobody needs isomorphism "just 'cause, y'know". Please refer to this fine article for the elaboration of the point. Do not go full frontal hipster, please. You need iso when time-to-presentation actually becomes a bottleneck in your conversion funnel. FFS, we do not even need to measure any conversion -- it's not like we are monetizing LogList in any way, shape or form. So, transition to isomorphic SPA will only complicate things for the devs without producing any value whatsoever.
And third -- writing isomorphic apps is not problem-solving hard. It's complicated, yes -- because there's a lot of mundane and boring stuff to take care of. So, not an achievement. A second-to-last bullet point in your CV, maybe.
Stay frosty. And never, ever, cut a deal with a dragon.