I'm a backer of Star Citizen and I've gotten my value out of backing it just from the community and all of the content that keeps coming out on the game. It's been $50 for me for hundreds of hours of entertainment so far, much better value than two tickets to the movies.
I do believe that there has been a bunch of mismanagement, which is a shame, but I still look forward to playing it sometime within the next 5-10 years. No game has ever been as ambitious as the scope of what Star Citizen aims to do.
I just came in here to sarcastically say something like: "This is a fascinating new business model where the product is DLC trailers and hype and the act of buying DLC but not playing anything".
I did not expect someone to say that non-ironically and be happy about it ...
Fusion.js is a javascript framework meant to be run on Node. There's nothing stopping you from calling out to other backends and asp.net if you stand up a Fusion.js frontend Node server.
Correct about Fusion.js being based on koa. We find that this fits really nicely within the plugin system. The diagram is complex, but we inject the render phase into the middleware stack. Everything before `await next()` is pre-render, and everything after `await next()` is post-render. It makes it very easy to reason about the lifecycle of a plugin, as everything is in one place.
Koa is an improvement over Express, but I think it would neat if the JavaScript ecosystem adopted an even more functional middleware style, like Python's WSGI, Ruby's Rack, Clojure's Ring, etc.
Conceptually it's simple: middleware is a function that typically accepts a downstream "app", and returns a new "app" which accepts a "request" and returns a "response":
const middleware = (app) =>
async (request) => {
// do stuff with request
const response = await app(request);
// do stuff with response
return response;
};
I worked on this idea way back in ~2009 (creatively called "JSGI" for the interface spec and "Jack" for an implementation) but promises weren't really a thing in JS, and async/await definitely wasn't a thing, so it was awkward.
More recently Michael Jackson had a project called Mach which was a similar idea, but it's no longer active either: https://github.com/mjackson/mach
As an aside, one of my favorite aspects of this style is having symmetric interfaces for HTTP servers and clients. You could do neat things like use a cache middleware for both a client and server, or write a simple HTTP proxy in a couple lines.
Anyway, with the addition of promises, async/await, and async iterators to JS I'm starting to dust off these old ideas. prototype here https://github.com/tlrobinson/twosixonesix
It was fun but hard to really make a convincing upgrade to Koa once you consider the rest of the ecosystem. For example, since Koa exposes Node's req/res, then you can still use existing Node/Express middleware.
I've been working with the Fusion.js team for the last year now, and I think it's evolved into a really interesting and modern web framework. Internally we've started rolling this framework to a few dozen web applications, and soon we will have hundreds of web apps running it. I think it's a great choice to use as a base for high-performance and complex web applications.
I had the same issue. An Airbnb host cancelled our reservation the day before our booking was supposed to start and Airbnb didn't help us out at all. We ended up paying quite a bit more for a hotel, but after going through that I'm happy to pay more in the future for professionalism and a guaranteed bed.
Electric unicycle? I own several. Some will even go over 50 km/h, though I don't dare go that fast. It's just safe to have the extra power when needed.
I asked about electric uni not for speed btw. I've seen a few and people were faster than traffic even at moderate speed (in city of course), looked relaxed as fk, the device was small. I don't know about energy efficiency but I was tempted to drop all other mode of transportation after seeing that.
It's great, but I can't stand the chaining syntax. I'm a bit biased, but I think that some suite with async/await will be the future. Here's something that I've been working on: https://github.com/KevinGrandon/ghostjs/
Love the idea behind the site! As an intermediate level Japanese speaker I think I could benefit a lot from it, but I had a few suggestions.
1 - Consider having one story from each difficulty available for free. The free intermediate article is a bit daunting for my current kanji level. I would be interested in signing up just for the beginner articles, but probably not without a preview.
2 - If time permits, consider having a button which can display a translation of the entire sentence. Satori reader has something similar and it's very useful when there's unknown grammar
Hope the site takes off, I would love to use and support it in the future.
Thank you so much for the feedback everyone! I posted this yesterday evening (in Japan) and so catching up now the next day.
kevining: That is a very good point about having free access to a book of each difficulty level. You are absolutely right, since with only an intermediate level book available for free, subscribing is a gamble as to whether there are books suitable for you (definitely don’t want to put people in that position).
I’ve updated the site now so that you can access 3 books (1 of each level) for free.
> 2 - If time permits, consider having a button which can display a translation of the entire sentence. Satori reader has something similar and it's very useful when there's unknown grammar
This is definitely something I’m thinking about. I toyed with the idea of translating each page myself and making that available at the bottom of each page. But scrolling to the bottom of the page is a hassle so I’d want to figure out something more integrated.
I also wasn’t sure how useful whole-sentence translations would be since I figured people using this would probably already have a good understanding of grammar. But perhaps these books are advanced enough to warrant whole-sentence translations regardless? Thoughts?
As someone with very little knowledge of the language, I definitely agree with your first point. It's hard for me to figure out if the product would be useful for me at my level since there's no "Easy" book available for free. I imagine that for an advanced learner it would be similar not knowing whether there's actually any new knowledge to be gained at their level.
You're cutting out a lot of the people in the middle and can show better ads. These ads should pay more, and both the publisher and user should make more than what they make today. (It's not hard to beat current payments to publishers, and users get no part of the pie right now).
Targeting can be much better if Brave gives the user the option to anonymously share information with them.
I do believe that there has been a bunch of mismanagement, which is a shame, but I still look forward to playing it sometime within the next 5-10 years. No game has ever been as ambitious as the scope of what Star Citizen aims to do.