Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
jakevn
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
15 ms
·
91.
▲
by
jakevn
12y ago
Does Aerospike offer transactions?
92.
▲
by
jakevn
12y ago
Nim provides you more flexibility than Go or Rust. Go is a GC'ed language and that's that. Like any other GC'ed language, the treatment for GC woes is palliative. Rust is designed around no GC and that's that. Of course,
93.
▲
by
jakevn
12y ago
Check out the top comment of this article: http://www.forbes.com/sites/jasonevangelho/2015/01/26/dell-x... A commenter pointed out to the author that Windows Indexing was responsible for significant
94.
▲
by
jakevn
12y ago
Apparently simply disabling Windows Indexing increased battery life from 7.5 hours to 9.5 hours in some tests.
95.
▲
by
jakevn
12y ago
He did have a concern about the data. His concern that was it was not peer-reviewed. Had the data come from someone with a proven track record in the field, he may have found it worth his time to peer review it himself. Appeal to authority
96.
▲
by
jakevn
12y ago
It would, however, be easy for a non-peer reviewed amateur to make a mistake. It's an appeal to authority, but in this case I don't believe it's a fallacy. Furthermore, since peer review is fallible, I don't believe Cla
97.
▲
by
jakevn
12y ago
I don't think it's snotty to be skeptical of the results. After all, their original hypothesis turned out to be incorrect. ODAP was not present in the seeds. Because the author took Clausen's consideration seriously, they wer
98.
▲
by
jakevn
12y ago
Were the ad to pose a security risk, and you, a paying user of Gmail would have no way to opt out, then sure.
99.
▲
by
jakevn
12y ago
I don't know much about ATS, but you've given me reason to investigate. Thank you!
100.
▲
by
jakevn
12y ago
There probably isn't a point to it, as we're likely trying to argue different points. I posit that using Haskell in such a way is a disservice to the language. If you want to code in such a way, why use Haskell? Haskell is plenty
101.
▲
by
jakevn
12y ago
The Rust code is both safer and faster at the cost of more keystrokes. I'm not certain the point of writing unsafe code in Haskell when there are better tools for the job. Haskell is fast enough as is and using it to hammer screws just
102.
▲
by
jakevn
12y ago
fannkuch-redux heavily utilizes unsafe operations on a mutable vector. binary-trees uses artificial strictness for the sake of the benchmark. Nine of the ten Haskell implementations are demonstrations of writing C in Haskell (without reachi
103.
▲
by
jakevn
12y ago
A glance at the source quickly reveals an unsafe implementation.
104.
▲
by
jakevn
12y ago
Their loss. It's illogical to fault entrepreneurs or the businesses they are a part of simply because one of an entrepreneur's core strengths and motivators is bringing projects off the ground. Likewise, it is illogical for fault
105.
▲
by
jakevn
12y ago
Thank you for this. I thought this-week-in-rust stopped a while ago. Very useful!
106.
▲
by
jakevn
12y ago
Also, I agree with you about the point of C being used in an OO fashion. I think this goes to show that a language doesn't need to specifically support objects/methods to wield in an OO-manner, it is just more inconvenient. Haskel
107.
▲
by
jakevn
12y ago
You have to draw the line somewhere. The structure of a typical OOP language program such Go, Rust, Java, C++, C#, etc. are not comparable to that of a typical Haskell program. All of the languages that are considered OO rely heavily on the
108.
▲
by
jakevn
12y ago
Inheritance is not necessary for OOP. For example, if you have: struct Cat { meow: String } impl Cat { fn talk(self) { println!(self.meow); } } fn main() { let bob = Cat { meow: "Mroowwwww!" };
109.
▲
by
jakevn
12y ago
I don't want to draw the line simply because I think it's too much a matter of opinion. To me, it's not about widely applicable ethics. I think companies should have the right to hire people from other countries and pay them
110.
▲
by
jakevn
12y ago
Companies can take advantage of situations for profit, and that's their right, but the argument needs to be qualified so that we aren't speaking past one another. Are we talking about "should be able to" or "it'
111.
▲
by
jakevn
12y ago
They have 31 blocking issues to take care of before 1.0 is a possibility: https://github.com/rust-lang/rust/milestones/1.0 The project has 2,100 open issues and 8,500 closed issues. The stability more or less
112.
▲
by
jakevn
12y ago
Were they actually fancy or cool, maybe. They're rather basic features among statically typed languages. Also, I'm not trying to say Go is bad or that I dislike it. It's simply not a modern language as far as design goes.
113.
▲
by
jakevn
12y ago
For better or worse, Go's design is anything but modern. It lacks things such as immutability and generics. It also perpetuates the mistake of including a run-time type error, null (nil).
114.
▲
by
jakevn
12y ago
> implicit parameters (C# doesn't have an analog to these that I can think of) C# allows default values for parameters, but it's not quite the same. Example of C# default value for parameter: static void Addition(int a, int
115.
▲
by
jakevn
12y ago
using System; public class Program { public class Person { private string _name; private int _age; public Person(string name, int age) { _name = name; _age = age; } public stati
116.
▲
by
jakevn
12y ago
It's simply less expressive. Just as Go is fine without generics, F# is fine without HKTs. It's a sad realization for those coming from a language that does support HKTs. Still a great language.
117.
▲
by
jakevn
12y ago
That's how it goes. A Scala dev will look at the Scala type signature and shrug. A C# dev will look at the C# type signature and shrug. As usual, unfamiliar things are difficult and familiar things are easy.
118.
▲
by
jakevn
12y ago
That's true. A talented C# dev will need to know co/contravariance as well as implicits considering they also exist in C#. In Scala, being familiar with these concepts is practically a necessity, though.
119.
▲
by
jakevn
12y ago
[SerializableAttribute] [ComVisibleAttribute(false)] public class Dictionary<TKey, TValue> : IDictionary<TKey, TValue>, ICollection<KeyValuePair<TKey, TValue>>, IDictionary, ICollection, IReadOnlyDictionary<TK