badbanana

Customer: What will this project cost? You: Five XL T-shirts.

Excuse the snark, but a lot of business decisions are made based on how much Project X will cost. You likely get paid based on time, so it's quite natural to gravitate toward time units - any intermediary unit is just an abstraction.

Not React code but SolidJS uses JSX to produce reactive code compile time in the same vein as Svelte.

Makers' Den | Full Stack JS Developer | Remote (Poland) | Full-time

We're a small remote-first software agency delivering web apps with BlitzJS/NextJS/ReactJS/NodeJS/Typescript. We're an agency by developers, for developers.

Read more: https://makersden.io/join

I also loved a similar article by my colleague.

He reverse engineered the api implementing the basic functionality, https://makersden.io/blog/reverse-engineering-styled-compone...

I played around 96-98. After that I continued hanging around as a wizard (coder) for a few years. Created some areas and relaunched the Barbarian guild (For Groo)

-Runeaxe Tuneaxe

Colleague of mine blogged about how to save on Gitlab runner costs using AWS Spot instances not too long ago, https://makersden.io/blog/reducing-gitlab-runner-cost-with-a...

Having used both React (with Typescript and Redux) and the latest Vue (with es6 and Vuex) I prefer React, and I don't even use React Native.

Vue is better for onboarding people more in tune with "classic" html + js development; and that's where the advantages end as far as I'm concerned. This might be a big win for some people.

The way I reason about it is that React is simple, Vue is easy. When you take into account Vue's templating language, React's api is small in comparison. A beginner won't know how to do some common use cases reading React's docs, when Vue might have a something built-in in its templating language (e.g. slots, or the component tag for dynamic components).

Slightly annoyed with Vuex too because of its slightly leaky abstraction. You have to remember to setup the properties you mutate so the reactivity will detect a change; and also remember not use array indexes arrays cause it can't detect changes otherwise. The array index thing will be fixed in the next version when they drop support for some older IE. Using Typescript would probably help a bit here, although Typescript being useless for checking Vue templates really feels like a huge chunk of its value is wasted.

Typescript is not currently available in the official blessed boilerplate which greatly affects its uptake in the Vue community.

Anyway, if you already know React, there is zero advantage in investing time in Vue.

Time constraints kept us from fleshing out all characters and descriptions.

"get container" should give some feedback that you're not able to pick it up, so that'd be a bug then.

Deploying the unix beard was a bug initially, but I left it in because I thought it was kind of funny.

The guy in the beginning looked like the kind of guy who'd be able to enter. Now if you only had similar facial hair somehow..

That's actually a super cool idea for a developer themed text game. Was it a web based game and is it still playable somewhere?

Yeah you're not the only one saying that. I guess text games aren't what the kids want these days :)

There should probably be a switch to turn off the bad screen effects.

If you wish to give feedback or ask questions; please go ahead. I and a workmate did this at a work-related hackathon a couple weeks ago.

How is Titanium a "HTML5 framework"?