331 karma · joined June 17, 2009
If only there were some kind of concept of typing, perhaps enforced by the language and statically applied, which would eliminate this class of error entirely...boy, that would be helpful in larger systems.
try {
mightFail();
} finally {
doCleanup();
}
instead of this: mightFail();
doCleanup();However, if the delay is caused by hitting the network for each search result on the backend (or something along those lines), maybe it would be nice to quickly return an initial barebones dataset and then the browser could do an async fetch of each record's details.
Yeah, totally makes sense to write your own search engine instead.
Or you could use Lucene and have a tiny bit of code in front of it that tacks on "~" to query terms first and save yourself some time. Or spend a few minutes reading the Lucene docs and find out how to do what you'd like to do. I've had the misfortune of dealing with homegrown search engines...it was laughable to see all that work (requiring a bunch of heavy-duty servers, lots of development time) replaced with a Lucene index that took half a day to get up and running with much better performance+features on a tiny VPS.
If your use case is teaching how to implement a garbage collector vs. a refcounting system, it is certainly much simpler to implement refcounting. If you are a systems programmer/writing a VM or compiler and do your work at a bare-metal level, then manual memory management/refcounting is probably your best choice.
For everyone else (let's guess over 90% of the programming population), using high-level GC'd languages is significantly simpler and more productive.
Parroting the article, I know: unless your entire app is Facebook-centric, be careful of tightly locking it to FB. If you must tie yourself to FB, think long and hard about doing so first and if you proceed make sure you've got a mitigation plan in place if things go south.
Shameless plug: check out our startup, http://yorn.com, which does exactly this.
"Status: 500 Internal Server Error"
Everyone has their preferred toolsets and frameworks and of course they should use what they feel is most effective. Case in point: my shop uses very little GWT - my coworkers prefer different tools (and often so do I; GWT is overkill IMHO unless you're building something big).
But this is all not really relevant to my point:
I was talking more about how the linked-to blog post was kind of web-development-101 stuff that everyone already knows and somehow, sadly, still received many upvotes/comments. I only brought GWT into the mix because some guy wrote a blog post about listening for URL hash changes and is presenting it as the future of web development, while (using GWT as an example) people with PhDs have written an optimizing Java to Javascript compiler and engineered very good solutions to difficult client-side web development problems that completely trivialize something as basic as hash change history tokens.
I agree that GWT is not friendly to UI people who are used to writing their own markup. But I would argue that a good UX person should be concerned with how the user interacts with the application (not necessarily by writing HTML and CSS by hand, but by sketching out the design on paper or Illustrator), and a framework like GWT often makes it simple to build complex UIs that would be difficult/labor-intensive to create and maintain with a traditional web dev stack. A decent developer should be capable of taking mockups from a designer and building out the rounded corners and other pretty bits himself in CSS.
http://es.reddit.com/r/gaming/comments/bbg9c/unlimited_detai...