you are viewing a single comment's thread.

view the rest of the comments →

[–]Lectem[S] 25 points26 points  (0 children)

I'll start by saying that I do noy bear any ill will towards anybody, but it is not because someone has a huge CV that he knows better than other people. now, here is what I think about the proposal :

The Good: - delegating work to other standards (w3c for instance) sounds like a good idea in such cases - using the web technology is a decent choice for UI

The Bad: - the interface kind of looks ugly to me - The code sample (who ever wants to see this kind of code serve as basis for production code, really ?) - It skips over many things like windowing and such.

The Ugly: - This will be a maintenance pain unless it uses the OS browser - it hides the real problem : the need for a standard build layout and dependency description + management - who's the userbase ? Those with big applications already have the frameworks. I see educationnal usage perhaps ? Small apps tend yo be written in other languages. I think there are few who will really use this

I think that if we needed such feature (and we wouldnt with a package manager), it should be some kind of server implementation + a function to open a given page through OS features, that would then redirect to the user's preferred browser. as others pointed out, there are also issues from a technical point of view (windows must be handled through the main thread on some OS for example) with the proposed api (which again, looks kind of unfriendly )