|
But isn't the whole point with HTML5 to be able to address nearly all platforms in a way that an application can be used?
If you only focus on native apps, you will probably end up supporting just a few platforms, leaving out a lot of potential users, which would be more than happy to have "just" an HTML5 app.
I won’t not use no double negatives.
|
|
|
|
|
I'd agree that is the point of HTML.
I think it's terribly mis-directed.
If you'd like give me an example of an application that would work just fine on a 3" screen, a 17" screen, and a 42" screen all while handling a keyboard, mouse, touch screen and XBOX 360 controller (something more than a video player) I'd find your argument more compelling. I'm talking a theoretical application here - it doesn't have to actually exist.
What I find difficult to swallow is the idea that some glorious standard is going to make all that possible while previous versions of the standard couldn't get a web page to render the same way in different browsers running on the same hardware and the same OS. Think about that for a moment - same hardware/same OS still doesn't work and yet they are reaching for something so far above and beyond that.
And that is the big problem.
When I go to spend $$$$ on applications I'm going to want something that is optimized in every way to work on the device I'm using. I don't want to play Left 4 Dead on my phone and I don't want to keep a contact list on my Xbox and I don't want to use Excel on my iPad. People who think that they need that are known as 'tools'.
|
|
|
|
|
I agree you, but...
MehGerbil wrote: give me an example of an application that would work just fine on a 3" screen, a
17" screen, and a 42" screen all while handling a keyboard, mouse, touch screen
and XBOX 360 controller
Probably a "Hello World" app would do it if you use any of the proposed interfaces to exit the app.
|
|
|
|
|
Philip F. wrote: But isn't the whole point with HTML5 to be able to address nearly all platforms in a way that an application can be used?
But, like every pipe dream of this sort before it (see: Java), it restricts you to the lowest common denominator. Native still rules for performance and features on every platform for any app that isn't a static webpage.
The end user doesn't give a toss if the developer had to have 18 code branches to keep up with it all, which you always end up doing with these "run everywhere" ideas anyway.
Look at me still talking when there's science to do
When I look out there it makes me glad I'm not you
|
|
|
|
|
In reality, HTML was only designed for presenting text, and maybe a few tables and images and links.
=====
\ | /
\|/
|
|-----|
| |
|_ |
_) | /
_) __/_
_) ____
| /|
| / |
| |
|-----|
|
=====
===
=
|
|
|
|
|
Gee. Seems to me that all of a sudden the concept of WPF/Silverlight with MVVM where can create different front ends (Views) for the same ViewModel makes sense. Create a different front end for different environments, but can keep all the plumbing
|
|
|
|
|
..Zuckerberg on "mistakes", without mentioning his IPO?
Bastard Programmer from Hell
if you can't read my code, try converting it here[^]
|
|
|
|
|
I wish all of my mistakes landed me several billion dollars.
|
|
|
|
|
At the extremely basic level, there are basically two good qualities that each programmer should strive for: programming skill and employee skill. Programming skill is basically the ability to write good, solid, performant, maintainable, and all-the-other-desireable-code-adjectives code. This is what coders tend to spend their time harping on and debating about and reading about. Employee skill is the ability to be a good employee and coworker. This means being responsive, being able to communicate well, hitting deadlines, being open to feedback, being able to explain complex things clearly, stuff like that. You can get far without being a great coder.
|
|
|
|
|
Rodrigo wouldn't do well in a team environment, but it's hard to believe that Gabriella "hasn't missed a deadline." Delivering buggy code on time isn't my definition of "meeting the deadline".
/ravi
|
|
|
|
|
I agree with you on this. But I've had many instances where management has said, "I don't care if it doesn't work, get it into production." Seen many instances where code that is not ready has been released because management is more concerned about meeting the deadline rather than the quality of the product.
|
|
|
|
|
Terrence Dorsey wrote: being able to explain complex things clearly,
"No",
"Yes"
"Maybe"
|
|
|
|
|
Amazing thoughts.
What seems to be the paradox is, you can do well without being a great coder. But to get inside [an organization] you need to have to be a great coder.
No one's going to recruit you just because you talk good english and meet deadlines.
-
Just that something can be done, doesn't mean it should be done. Respect developers and their efforts!
Jk
|
|
|
|
|
Terrence Dorsey wrote: You can get far without being a great coder.
I know! Been cleaning up behind them for ages..
What the man means with "being a good employee" does not add up with being a good coder. You're a good employee if you don't complain about the coffee and don't speak against the boss. You're a good coder if you tell the boss that VB6 is dead and that his new Skynet will NOT be developed using a dead language, unless all the documentation will be in Latin.
Bastard Programmer from Hell
if you can't read my code, try converting it here[^]
|
|
|
|
|
so many mixed up "Project Management Skill", "Communication Skill" and "Teamwork" which covers everything from correct grammar to arse kissing (imagine all the other buzz words invented by the HR and management)
Good coder = Good programming skill, PERIOD.
That's the kind of people I looked for two years ago when I hired developers for our group
dev
|
|
|
|
|
Quote: However, the point is that managers are the people you need to impress to get jobs and promotions and raises and pats on the back, so in this scenario, Gabriella comes out way ahead.
I don't see the issue here. Gabriella is clearly more suited for management, so she gets promoted into it. Rodrigo continues doing what he does best. Everyone ends up where their skills are most valuable.
|
|
|
|
|
In broad terms, functional claiming refers to writing patent claims that cover the broader function enabled by an invention rather than writing claims to the specific embodiment developed or contemplated by the inventor. In other words, instead of erecting a signpost that points others directly to the invention, functional claiming is akin to building a wide fence to surround the invention in an attempt to claim as much territory as possible. Tech patents, the Wright brothers and open source software.
|
|
|
|
|
The usually quiet world of mathematics is abuzz with a claim that one of the most important problems in number theory has been solved. Mathematician Shinichi Mochizuki of Kyoto University in Japan has released a 500-page proof of the abc conjecture, which proposes a relationship between whole numbers — a 'Diophantine' problem. 1 + 1 = two math stories in a single newsletter. How odd...
|
|
|
|
|
Aghh! He beat me to it.
I actually tried my hand on this.
|
|
|
|
|
Suppose you have a very large dataset - far too large to hold in memory - with duplicate entries. You want to know how many duplicate entries, but your data isn't sorted, and it's big enough that sorting and counting is impractical. How do you estimate how many unique entries the dataset contains? It's easy to see how this could be useful in many applications, such as query planning in a database: the best query plan can depend greatly on not just how many values there are in total, but also on how many unique values there are. By my rough estimate, I believe you'll like this article.
|
|
|
|
|
Terrence Dorsey wrote: By my rough estimate, I believe you'll like this article.
Yes, I did. Very interesting article
"Any sort of work in VB6 is bound to provide several WTF moments." - Christian Graus
|
|
|
|
|
The issue was naming. My partner wanted to name an abstraction after it's implementation. It's natural. You're in the middle of implementing binary search, so you call the function binarySearch. This is where the ummm... stimulating conversation started. Take a step back, I said. Think about this from the perspective of the caller, I said. "Why?" he said. Once again, what looks like a technical problem--function naming--turns out to be deeply, personally human.
|
|
|
|
|
If your corporate policy prohibits surfing facebook, you won't be able to view Kents article.
|
|
|
|
|
The very first text-based adventure game, titled “Colossal Cave Adventure” was written and developed by William Crowther in 1976. Crowther went through an awful divorce and needed some distraction. He also wanted to keep the connection to his two children up and running. Like any cool programmer/father would do, he created a game for them — “Colossal Cave Adventure”. Originally written in Fortran and developed for the PDP-10 computer family, the game became a classic on several different systems. During the ’80s, it was translated into many different IF programming languages, including the most important one in IF history: ZIL, short for Z-Machine Interpreter Language. Text adventures are alive a kicking. Play one today... or write your own!
|
|
|
|
|
Terrence Dorsey wrote: or write your own! Excellent idea - see here[^].
/ravi
|
|
|
|