Pacabel

19 ms·

121.
by Pacabel 12y ago
The reasoning in your first paragraph never really seems very sensible or realistic. So people with very limited financial resources to begin with will be able to buy ultra-low-end phones that offer poor performance and a poor user experien
122.
by Pacabel 12y ago
Are there any screenshots showing side-by-side comparisons between the same app implemented using this technology running on the different platforms it supports? I looked quickly through the article and the NativeScript web site, but couldn
123.
by Pacabel 12y ago
It's clear that Rust isn't stable yet, and won't be for a long time. It's impossible for me or anyone else to be incorrect when we point out that very real fact. If you feel the need to vote down perfectly legitimate com
124.
by Pacabel 12y ago
Firefox OS is yet another example of Mozilla apparently thinking that ideological purity alone will somehow entice users into adopting an otherwise average-to-bad software offering. That isn't how reality works, though, obviously. Out
125.
by Pacabel 12y ago
I wouldn't say that it necessarily is. But Android does offer the NDK and the upcoming ART runtime, which get far closer to native code than what we're seeing from HTML5/JavaScript/CSS.
126.
by Pacabel 12y ago
How do you figure there are "fewer layers"? Both are built upon Linux. So we can say that they're pretty much equivalent at that level. Then there is a runtime and libraries providing common functionality above that. Again, w
127.
by Pacabel 12y ago
The reviews I've read about the existing Firefox OS phones, which have reportedly cost well over $25, have not been very encouraging. Pretty much all of them have pointed out that the hardware is quite poor, and this results in a rathe
128.
by Pacabel 12y ago
The Rust mis-votings are quite absurd. In no way can Rust be considered "stable". The most recent version is 0.10 (that is, it's still very pre-1.0), it's undergoing significant breaking changes on an ongoing basis, and
129.
by Pacabel 12y ago
Don't worry about the downvotes. Things have gotten pretty bad around here lately, especially after the whole "downvote if you disagree" policy was encouraged. A lot of totally correct and perfectly valid commentary ends up g
130.
by Pacabel 12y ago
That's obviously not what I wrote, and you would know this had you bothered to read my comment. I'm saying that such features alone do not actually guarantee safety, if the language's implementation happens to have flaws. The
131.
by Pacabel 12y ago
Right, that is an option, but it unfortunately involves some effort from the user. This is effort that wasn't needed before. In my opinion, having to expend this extra effort even just once ends up harming the user experience relative
132.
by Pacabel 12y ago
Why is that comment getting voted down? Everything it states is true. Rust isn't stable. It really hasn't seen any serious use. Even the Rust home page itself currently states, "Rust is a work-in-progress and may do anything
133.
by Pacabel 12y ago
I'd prefer to see how it fares in the real world before jumping to such conclusions like you seem to be so willing to do. You may not have been around to experience it first-hand, but we heard a lot of claims made back in the 1990s abo
134.
by Pacabel 12y ago
Having been in industry for a long time, I think that something like Rust would be hugely beneficial. It very well could solve some very real problems. I bring this up again and again because I'd rather not see Rust fail. I'd much
135.
by Pacabel 12y ago
I think it has. Visually, the contrast is worse now than it was before. While this may be "trendy", it does harm usability. The default coloring of the old results page was much easier to look at, as well. It made it easier to dif
136.
by Pacabel 12y ago
I, and many others, do use something else. That's the big problem facing Rust, whether or not its creators wish to admit this fact. There are numerous alternatives to Rust that offer many of its benefits, but they're usable today.
137.
by Pacabel 12y ago
Well, we aren't actually seeing stabilization when it comes to Rust. Assuming this stabilization actually does happen, whether it happens in public or private is irrelevant. What matters is that we've seen C++ stabilize. We'v
138.
by Pacabel 12y ago
Resort to name-calling if you really must. None of that will change reality. Rust is not stable, as you yourself have readily admitted. What I've unfortunately had to be pointing out for such a long time now is absolutely correct. We&#
139.
by Pacabel 12y ago
Are you honestly suggesting that Rust is stable at this point? I think that the recent, and very disruptive, ~ and box changes should completely dispel that notion. I'm merely pointing out the reality of the current situation, which so
140.
by Pacabel 12y ago
I think you may be aiming for a level of safety, or perhaps a notion of "perfection", that isn't practically obtainable. The recent, and rather disruptive, box changes are a good example of this. We see change, and those of u
141.
by Pacabel 12y ago
One thing that worries me about DDG is their recent UI redesign. It felt, and still feels, to me very much like the failed UI redesigns we've seen from Google as of late. Even after giving it some time, I still don't think I'
142.
by Pacabel 12y ago
My apologies, I didn't realize that expecting a programming language to have a stable syntax, stable semantics, a stable standard library and at least one stable and robust implementation before using it seriously in industry was merel
143.
by Pacabel 12y ago
I think you're putting words into his mouth, and perhaps intentionally misrepresenting what he wrote. Swift was announced just a few hours ago. While we can make assumptions about its safety based on its feature set, or we can assume t
144.
by Pacabel 12y ago
Yes, I do agree that the situation is improving across the board. But as an industry, we need practical solutions that are available now, even if somewhat flawed. We need languages we can use today, and know that the code we write today wil
145.
by Pacabel 12y ago
What you're saying is perhaps ideal. The unfortunate reality, however, is that we really aren't seeing the "once Rust is mature" part actually happening. There is still a large amount of change happening to the language
146.
by Pacabel 12y ago
So what other language can we use today on basically any imaginable platform, while still retaining the extreme degree of control, the excellent interoperability, and the near-optimal runtime performance of C? Some will say Rust, but we&#x2
147.
by Pacabel 12y ago
The similarity to Rust should scare the hell out of Rust's creators and proponents. Swift could very well render Rust almost totally irrelevant within the OS X and iOS sphere of software development. If we end up eventually seeing Swif
148.
by Pacabel 12y ago
Do you still have your original comment? If you do, you should seriously consider posting it. It's difficult to discuss this topic with you if you intentionally avoid posting anything of substance, and instead throw out accusations of
149.
by Pacabel 12y ago
If it was "forced", then she would have had absolutely no choice in the matter. It probably wasn't physical, as we've already determined. It likely didn't involve any sort of risk to her job outside of her control,
150.
by Pacabel 12y ago
I very much doubt it was a "requirement" in any sense. My guess is that the co-worker from India totally misconstrued the situation, due to not having a good understanding of American culture. I could easily see the dialog being q

More ›