pbsdp

16 ms·

121.
by pbsdp 13y ago
http://en.m.wikipedia.org/wiki/Wire_wrap
122.
by pbsdp 13y ago
The problem with ASN.1 was ASN.1, BER, and DER themselves not the fact that a binary encoding was used.
123.
by pbsdp 13y ago
What do you think 'native' platforms are? They're the platforms built to support app development.
124.
by pbsdp 13y ago
And we've wasted vast mountains of money dealing with the resulting brokenness of the web. Those people would have figured out how to ship a web page; they'd just would have had so much trouble figuring out why one they shipped wa
125.
by pbsdp 13y ago
HTTP is already painfully complex to implement correctly. It's also a terribly wasteful and poor engineered protocol for anything other than fetching documents.
126.
by pbsdp 13y ago
All of which are absolutely terrible looking applications with broken platform UX on Mac OS X.
127.
by pbsdp 13y ago
Said the guy whose only written Windows (and maybe Linux) apps.
128.
by pbsdp 13y ago
There's less room to fudge funny-money numbers if you actually have revenue.
129.
by pbsdp 13y ago
> Either way the fact that you don't instantly recognize Qt apps when you see them is proof positive, as they are out there in much higher numbers than you seem to realize... No, they really aren't.
130.
by pbsdp 13y ago
If by 'worked' you mean that you were still able to sell it. It doesn't fit into the platform and nobody actually likes the result, but if you have a market niche, you can get away with it -- until a competitor appears that a
131.
by pbsdp 13y ago
Yes. And users still don't care, and they're the ones that pay for the work.
132.
by pbsdp 13y ago
What does that have to do with the platform native widgets and UX? In fact, GL and the native UX interacts poorly, consistently, on both platforms.
133.
by pbsdp 13y ago
> Qt and QML is just not native(widgets will look different, etc), but it will perform well. Yes, which is not what people want. They want apps that fit in with the larger platform and exploit it's featureset. We already went thro
134.
by pbsdp 13y ago
> Isn't it premature to declare this a categorical disadvantage for the user? No, we've had about 10-15 years to prove, repeatedly, that "write once, run everywhere" UI never works. > I would have more time avai
135.
by pbsdp 13y ago
How are websites holding up against the native App Store apps for apps ?
136.
by pbsdp 13y ago
"... squash anybody who tries to add value to their product" Add value? They're extracting value. > I will be avoiding use of Craig's List's services until I feel like they are allowing people to innovate off
137.
by pbsdp 13y ago
"I wish my apps were written using a poorly integrated non-native toolkit" said no actual user, ever. Nobody wants a Qt-based application port , for most of the same reason nobody wanted a (Java) Swing-based port . They don&#x
138.
by pbsdp 13y ago
Most of the complex HTTP infrastructure exists to support a the complex HTTP protocol. Get rid of HTTP, and pretty much all of the complexity of the HTTP stack evaporates.
139.
by pbsdp 13y ago
> If you are looking to make money off a mobile app (not establish saas mobile extension) rapidly launch MVPs of your apps to see if there is any demand. Don't invest in perfect designs and ux until you've validated that there
140.
by pbsdp 13y ago
Getting statistically useful data out of this will be difficult. A/B tests can tell you which of a set if options performs better for a measurable metric, but not why , and without no visibility into 'metrics' you can'
141.
by pbsdp 13y ago
Mining user profiles for targeted AdSense ads is just the tiniest part of the problem. Massive government spying revelations based on tapping into centralized infrastructure at cooperative organizations that maintain broad cross-web and cr
142.
by pbsdp 13y ago
The article vastly overstates the ability for normal people to avoid survellience. We technologists are building the centralized industrial survellience state by voluntarily feeding metadata and content on our users to centralized analyti
143.
by pbsdp 13y ago
> ... they'd probably freak out thinking it was some evil Google scheme to mine data when in fact, all that is simply a byproduct of any reasonable logging or analytics solution that is not special to Google at all. If that's
144.
by pbsdp 13y ago
"... deploy those apps to others through the Propeller app on an iPhone ..." This is explicitly forbidden in the iPhone app store. Actually distributing these apps will be a problem; code signing and adhoc and/or appstore dis
145.
by pbsdp 13y ago
A big difference is that the exploit can't be pushed to every single device in the world that is running the software in question and phoning home for updates.
146.
by pbsdp 13y ago
No, it wouldn't have. Manual updating: - Spreads the exposure time, creating a much larger window in which updates may be deployed, reducing the number of systems affected, and reducing the likelihood of a targeted attack succeeding. -
147.
by pbsdp 13y ago
This is a pretty compelling argument against silent automatic updates.
148.
by pbsdp 13y ago
> - Less accessible. Objective C is a strange, low-level, difficult-to-learn, niche language used only for mac development. It's not hard for someone that already knows C, or really any other language. The learning curve is in pla
149.
by pbsdp 13y ago
> Surely not in ease of development? Nope. Building a complex application in JS+HTML+CSS is still an enormously painful undertaking. > Ease of learning? Also nope. Complex applications are still complex. > Ease/portabil
150.
by pbsdp 13y ago
It's hard to dream big about the browsers getting the modern iteration of something we've had in some form since 1992.

More ›