artificialidiot

Vala is not suitable for anything production ready because of its half assed memory management semantics. I believe it is better to invest in C++11 at this point than vala. At least, it would be a little bit easier to use libraries which don't have a binding.

Therefore, I offer my services for a measly 10 million dollars per year to employ my skills to:

* Fend off adverse technical proposals.

* Coalesce around market-making implementation guidelines and creative standards.

* Create common ground with developer to reduce costly friction in the content delivery chain.

* Share best practices that foster audience growth.

* Generate industry-wide research and thought leadership that would solidify Interactive as the leading consultancy

* Create countervailing force to balance power of other free software, privacy advocates, and de facto internet standards groups.

I think he's trying to tell us something. :)

Designed for el cheapo shared hosts with php. No database, just plain text files in posts directory. Minimal features. Write in markdown. Antisocial, because no one reads mine.

Really, I am rather proud of it no matter how crappy it is. Everyone is welcome to bash it for any reason on twitter or facebook. All feedback will be considered carefully.

Learn java if you touch JVM, there is no escape.

Way to get volunteers to fix it.

I can be selfish too.

There is no fundamental difference between either approaches except the runtime cost. If you need conditonals, use them. If you need a lookup table, use them. Keep the code predictable.

Forward your thanks to the intrusive ad networks, spammers and other cretin who've been treating users badly for the last few decades, attracting hostile attention to the advertising practices.

People woke up to the fact that they are in control of the content coming through their wires thanks to the versatility of the contemporary computers. There is no return.

You should embrace current realities of the market you so love to invoke for every other subject and start innovating and distrupting. Failing that, stick with the proven ad channels such as iDevices, other locked down devices, social stalking services, local tv and radio channels and papers.

You won't be missed.

Sincerely, Internet users

2. When Amazon decides WoW gold is good enough too.

Maybe we should update CSS to include object oriented features too. Then we can have abstract factory methods for our reusable components. Throw in an optional type checker for good measure while we are at it.

Please people, CSS and HTML only ever have had a single layout algorithm. Maybe it is not terribly flexible but it is good for limited width and unlimited unknown height presentation of a single stream of content. If your content genuinely calls for a different layout, please consider using something else other than CSS and HTML.

While I appreciate the endless efforts to workaround and improve the layout capabilities of CSS, may I suggest embracing the limited nature of this stack and design accordingly?

Maybe, if we admit the "content" arrive, is rendered and consumed sequentially, we would relieve ourselves the burden of beating CSS into submission whenever we want to diverge; with the added benefit of making life easier for those who can't see.

You wouldn't shy away from a little bit of challenge of learning something more suitable for you purposes, right?

They can alternatively just require at least opengl es 2.0 support installed through gfx driver, thus only working on desktop machines. Not that it will make their plans of phone+tablet+desktop unification easier but, hey, it might shut up whining hipster developers for at least a few years until the realization that MS intentionally underdelivers dawns on them.

I see no reason why we should stop using javascript as a scripting language for DOM.

I see no reason why we should stop building applications that only calls for simple HTML forms.

Traditional web will be alive and well as long as we continue to speak HTTP freely.

There are modern options though:

1. Disable unnecessary stuff on your IDE. 2. Don't use a IDE, use a dedicated editor. 3. Don't use an editor from a VGA console. 4. Stop pretending you code on a vt100.

I see no wrong with a sensibly long line which is longer than 79, just as I see no wrong in keeping multiple parts of code visible at all times. There shouldn't be hard limits or carved to stone guidelines.