hxa7241

40 ms·

1. 331.▲
   Software Engineering And Civil Engineering(hxa.name)

   2 points by hxa7241 18y ago|0 comments
2. 332.▲
   by hxa7241 18y ago

   Receiving, as an ebook publisher.
3. 333.▲
   by hxa7241 18y ago

   Last time I looked, Amazon required a USA bank account for payments. That is annoying...
4. 334.▲
   by hxa7241 18y ago

   late 1990s -- looking at the HTML and outward links
5. 335.▲
   by hxa7241 18y ago

   But this doesn't address the explicit, simple, standardisation of app/interaction structure. If it is defined in a full procedural language, it is obscure and un-manipulable. The application structure should be moved as much as possible int
6. 336.▲
   by hxa7241 18y ago

   The cost of the checks should balance the cost of the risks. Those are not always determinate or exactly estimable, but, statistically, that would be a simple basis of a rational approach. Wouldn't it?
7. 337.▲
   by hxa7241 18y ago

   There is a major, fundamental problem with moving the definition of web applications to being JavaScript/Python/Java-centered. It offends one of Berners-Lee's principles of web architecture: the 'principle of least power' http://www.w3.org
8. 338.▲
   by hxa7241 18y ago

   Didn't they design or build a Java co-processor about 10 years ago -- what happened with that?
9. 339.▲
   by hxa7241 18y ago

   Brooks somewhere notes that the only/best candidate for a 'silver bullet' is reuse -- and I see that as the backbone of the article, or at least the proposed vision. Essential complexity cannot be eliminated, of course, but it can be avoide