huula

Great work! Is it ok for commercial use?

Every example provided in the article is model and training data specific, it only tells one thing, your data is not telling the truth, so why not getting better data.

I'm using scala Slick for huula, should I have this concern too since the development there seems really like just a one company effort.

You are not alone. How would they handle the dust and noise which comes so tightly with high performance servers?

As a user of GitLab who commits several times everyday, I have all the respect for the great work you guys have done. Keep hacking and don't worry!

I once rm-ed my home directory when I was writing and testing a script, but turned out the stuff like .m2, .ivy2 are huge and they are the first ones by default to be deleted by 'rm -rf'. So they kind of gave me some buffering time to figure out that something was wrong.

Thanks!

Thanks for your kind words! Yes, thegrid guys are really good at advertising, they had a very successful kickstarter campaign, but they failed to deliver an actual product. See this: https://news.ycombinator.com/item?id=10140724

Huula focuses more on the technology and we really want to build something that's intelligent and amazing. CSSRooster is just our first step, there are certainly a lot of technical challenges to be solved, but I believe we'll have something soon, stay tuned.

Hey, really thank you for your interest! Since this project will be part of Huula which I'm trying to build a business upon, it will not be released for now (will do when I fail tho, so stay tuned! ;D)

But, here's an example that's similar to CSSRooster's model https://github.com/fchollet/keras/blob/master/examples/imdb_..., for the part that's different (mostly data preprocessing), you need to write your own according to your data anyway. Do let me know if you have any questions.

Good question! To be frankly, not much use for a normal development flow (maybe you can use it as a check to see how much compliant is your code with the 'standard'), but it's going to be used by Huula's editor to better identify different elements on a web page, the reason why this is useful there is because Huula editor has all the symantic and visual properties of every element and it can use this information to generate the same class names for similar elements.

> Is it discouraged to use server-side rendering?

No, it's not! But it's discouraged to use it as the only rendering layer.

Server side rendering has its unbeatable advantages - speed. That's why you can view content on https://huu.la within second, similar methods are used by Google, Twitter, etc. A lot of people might say, we have faster networks now. Believe me, even at Bay Area, it takes time to, first, download your powerful client-side library, second, bootstrap your powerful client-side app, and third, call XHRs to fetch your data. Not to mention there are so many mobiles, with even less capable networks.

So from my experience developing Huula, I would recommend using a combined approach. For places where speed is critical, for example your landing page, help page, use server side rendering; for places where a lot of user interactions will happen, use client-side rendering since it gives your more support for componentization if that's a word and user interactions.

Nice work! Really like the way you provide color palette instead wild crazy color selector for your user, that simplifies things so much! However, A common problem with this product and a lot of other template based website builders like Squarespace, Weebly, Wix is, you will end up creating so many sites that looks just the same. If you just want a clone, then I have nothing to say. But more customization and more unique intelligent generation certainly needs advanced models other than naive templates.

Hey, this is the guy whose dissertation talk I went to several months ago, which is on the same topic!

Uh, thanks, but 304 Moved Permanently also has a similar effect right?

@marc_firedrop Mind if you can share what your training set is?

Just curious, this looks like some already supported feature of nginx, only that it's supported through redirection. Is this a redirection too or a protocol change? How will that be reflected on the address bar?

I saw the prototype of Pokemon Go in 2014 as an April 1st campaign by Google Maps, surely this is a very tight bond with Google. I won't worry about it either.

Cool! It would be great if it could a little bit faster tho.

An atmega328p, how big should it be LOL

I always like Google's serious attitude towards engineering, even after they have made some mistakes, they never try to hide anything.

Hey man, take it easy ;)

Huula does solve the problem the user is facing, so by any means, this is not spam at all.

And BTW, we are targeting different segments. You want to serve developers, I want to serve non-tech person, like HRs, Operations, etc. So technically, we are not competitors!

[Shameless Self-Promotion] For guys who don't want to write code to create smart popovers/tours in rich text, video, image, etc. I created a free online service https://huu.la .

p.s. It doesn't mess up with the DOM element you are creating for.

Totally understand your pain. Did you try https://huu.la? It never messes up with the user's page DOMs and you don't even need to write code to use it.

Completely agree! Hope Meteor community would seriously consider this.

+1. Meteor should try to optimize their build time (for example, when I just changed one JS file, there's no point to spend more than 20 seconds to reload a simple page) and be frontend agnostic. The main thing I like Meteor (and also why I'm still sticking around) is how it manages data and the DDP stuff. Never a fan of Blaze, but certainly not sure about this "future vision".

Love Spark! great works, folks!

I heard it's closed already last year?

You are right, http://huu.la is using server rendering and prefetching technique, which makes the ux x00% better than this one.

You are right, it's typo, just for expressing the ideas. Huh, looks like I'm not the first one try this. Good to know. Thanks!

OO is important in almost all cases. Because for a cohesive system, you will always have some part to share across components.