222 karma · joined January 4, 2012
And for that matter I really appreciate Go and its simplicity.
Regarding the original webpage of Norvig's spelling corrector, I think it is not up to date as I remember browsing the web and finding some shorter versions in other languages.
I've shortened the Python version to 14/15 lines using some features of Python3.
The data hasn't been updated since 2006 but the change should not be that much different. I've contacted the author in the past, for some technical explanation:
The NOAA data is the light source data. It uses the light source data as input to a model of light propagation in the atmosphere to estimate the light pollution.
This takes into account that the light pollution from a town or city (or natural gas field!) can affect the level of light pollution at locations far removed from the light source.
Technically, my light pollution atlas is the amount of artificial sky brightness at zenith.
Apparently I'm a saint, or I don't comment that much.
I want to make the world a better place.
I work as a Java Developer/Architect with 7+ years of experiences, with very good skills in both backend (Java, Spring, Oracle, PostgreSQL, redis) and frontend (JS, jQuery, AngularJS, HTML5, etc..), REST/SOAP, plus some mobile stuff (Android, ionic) and all the tooling that goes with Java (maven, sbt, ...).
I'll probably give it a try. I like the DRY part regarding the injected dependencies.
I had 50MB of data, and it took at least one minute to process the JSON file.
I also think that both this and HTTPS are mandatory, but since it's on your roadmap that's good enough.
Yes apples and oranges. They taste different, because they are.
> In my experience the OPPOSITE is normal. If XML is invalid but still makes sense, you treat it as valid, because if you don't, your competitors will.
If this is a business requirement you would do the same for JSON.
> If you don't think somebody would throw invalid XML at your app and not expect it to work then you've clearly never worked with XML seriously.
Nope, if you have a customer sending you an XML which should validate against a predefined schema, no, hell no. I've worked for the European office of publications, and the web services were just receiving tons of XML on a daily basis. And you know what, invalid XML were rejected that's as simple as that. If you don't respect the supplied schema, retry when correct.
> docbook IS XML.
Docbook USES XML.
Last but not least, HTML is not XML, HTML is not a subset of XML. Permissiveness has nothing to do with web services acceptance of invalid schemas.
If you call a Google service whether it uses SOAP (so XML) or REST, if the request body is invalid, you'll be rejected either way. The SOAP one won't try to parse more or resolve issues just because it is XML based.
> Yes you do, because otherwise people will treat your application as buggy
You are mistaking HTML/Browser rendering and XML parsing. An application that parses XML for book rendering, or whatever the hell the purpose of the application is, will fail on invalid input, whether it is because of invalid tag nesting or schema invalidity.
That is NORMAL, and you would do the same with JSON, so that's not because of history of HTML and IE/Netscape/whatever that you need to change your mind about XML.
> If resumes are going to be done in markup it's so they can be consumed by web services
So if a web service was to accept a specific type of XML, it would certainly need to be made valid, if a client does not conform why the fuck do you want your service to be permissive? Seriously.
You can make a service that accepts the resume schema directly, or embed it in a CDATA if you want to.
> I would rather use LaTeX for publishing content. It's complex, but it can handle layout beautifully
Talking about apple and oranges. XML and docbook are not the same.
Java has an enormous ecosystem, is fast, is stable, has static typing, has more tooling than anything else, is easier to learn, does not have all the gotchas that Javascript has. I don't consider Java a worse language at all.
I use Java since a decade, and frankly I don't understand that rage against it while it is a totally valid option to start a project with, even a startup. If you want to get RESTful and all there's everything you need, etc.
Take it from a guy doing some Golang since more than one year and enjoying it a lot, also well versed in Python, Javascript, and even OCaml.
In fact, the time it took me to write this comment, I decided that I don't care anymore. Use what you need for the job and be prepared to change when something new is out and have a real impact on what you do.
This is just plain wrong to force someone with your new hype and vague idea of how a web application should be developed using only your new hipster framework of choice and nothing else.
There are tons of way you can write a web application, that's why open source is cool, chose the one that pleases you and have fun with it, but stop trying to prevent others using anything else but what you judge to be the best.
It's the same as getting between 30 and 40 years of an experimented developer's average salary where I work, so it would mean that I can live exactly as I do now (and I can't complain), but at home without needing to work anymore. Just good money to spend with family, travelling or improving your knowledge. Seems like a good deal to me.
But as I said in the message the site is usable so I don't really care that much, it's just some polishing that would make it greater.