Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
sreque
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
15 ms
·
121.
▲
by
sreque
9y ago
I responded to someone else who asked the same question in this thread. Can I have an update now? :)
122.
▲
by
sreque
9y ago
Sorry. I haven't had a chance to reply all day. The biggest reason I think Eclipse is better is because it has automatic incremental compilation built in. This feature is an absolute game changer in productivity. Visual Studio doesn&#x
123.
▲
by
sreque
9y ago
This post makes me very sad. I am often reminded that the best tech rarely wins. I've never had to use Intellij until my current job, but it is more obvious to me than ever than Eclipse, at least for Java development, is superior to In
124.
▲
by
sreque
9y ago
For teaching purposes in a university I don't know if rust would be better or not. Keep in mind that the goal isn't necessarily to learn C the language; it's to learn enough of the core language to explore things like: * How
125.
▲
by
sreque
9y ago
Knowing C has made me a better and much more versatile programmer than I would be without it. For instance, a while back I had to diagnose a JVM core dumping sporadically, and I was able to use my knowledge of C to try to recover valid retu
126.
▲
by
sreque
9y ago
Spawning a process, even if its just vfork() followed by exec(), is very very expensive compared to spawning a thread, and even then most apps created threads on startup and then just cache them for the lifetime of the application. Spawning
127.
▲
by
sreque
9y ago
I'm only saying that it would take more effort and place more burden on a developer to figure out how to do all that in their programming language rather than just implement a function. I'm surprised this is a contested point. Tel
128.
▲
by
sreque
9y ago
part of the "magic" of Lambda is making it easy to use from your programming language of choice. If they made a lower-level model, like, for example, "we start up your binary, and it needs to bind to port X, then we'll s
129.
▲
by
sreque
9y ago
I definitely agree with this stance, and would say that languages like C# and golang have a weaker runtime but try to make up for it in other ways, often surpassing Java in certain areas. For instance, both languages have stack-allocated ty
130.
▲
by
sreque
9y ago
I really enjoy seeing this debate because I hope more anti-ORMers unite and we see less use of ORMs in future projects. There are other disadvantages of ORMs that I haven't seen mentioned much: 1) low-level performance. Even if, and it
131.
▲
by
sreque
9y ago
So, to start, I would say that I agree with you that I like my DI logic for my application centralized, whether it's in a single or few classes or in a single or few XML files. On the other hand, people who use @Autowired or @Inject ar
132.
▲
by
sreque
9y ago
It's always ironic to me that people think implicits reduce code clarity, and yet those same people use runtime DI frameworks and possibly AOP. Scala implicits can in my opinion be thought of as a simple compile-time lexically-scoped D
133.
▲
by
sreque
9y ago
http://matt.might.net/articles/best-programming-languages/ "I don't think Java is all that bad, and I can enjoy well-done object-oriented programming." This is probably the most accurate opinion of
134.
▲
by
sreque
9y ago
It's also far far slower performance-wise to put it on the heap. GoLang also does stack-copying with their continuations, and it's probably the best implementation strategy we have right now. There were a number of interesting pro
135.
▲
by
sreque
9y ago
By programming using synchronous blocking code within a single thread, of course.
136.
▲
by
sreque
9y ago
It's still "callback hell" because you're still fundamentally writing code where you invoke an API and pass in a callback to handle the results. The fact that the callback you pass in happens to be a promise that allows
137.
▲
by
sreque
9y ago
C# is fairly efficient while still having managed memory. And, of course, golang was designed to hit the sweet spot of automatic memory management, decent performance, and non-blocking I/O. Beyond that, there's things like Erlang
138.
▲
by
sreque
9y ago
I have written servers in C with epoll that were used in production, thank you. And yes, I'm aware of async/await and its limitations. State-machine-style transformations from blocking-looking code to non-blocking code are definit
139.
▲
by
sreque
9y ago
I'm well aware of promises, thank you. I'm also well aware that there's very little difference in reality between a promise-based style of coding and a callback one. You still lose stack continuity, it's still much harde
140.
▲
by
sreque
9y ago
Node.js brings callback hell to the serverside world of threads and we're supposed to be grateful? It's like you don't know the history of computing. Callback-based code was the original programming model in UNIX dating back
141.
▲
by
sreque
9y ago
I spent a lot of time analyzing the startup time of Java, Python, and Node.js. For any real-world program, startup time is entirely dominated by time taken to load code into memory, which in python is import statements. Also, as slow as Pyt
142.
▲
by
sreque
9y ago
One source of high load average spikes that I've seen in my job is when a process crashes and generates a core dump. While the core dump is being written, all threads in the process are in the TASK_UNINTERRUPTIBLE state even though the
143.
▲
by
sreque
9y ago
I've ran into this problem before. IMO this issue has nothing to do with go and the solution is straightforward. Simply create a sub-process whenever entering a new namespace because the operation isn't concurrency safe within a
144.
▲
by
sreque
9y ago
I developed at a Windows-centric shop for several years using C# and Visual Studio, and I can personally attest, at least in 2013, that stock Visual Studio is pretty far behind Java IDEs in its capabilities. At the time everyone I talked to
145.
▲
by
sreque
9y ago
At a high-level, async/await lets you write non-blocking code as if it were blocking. Golang has a huge advantage here because the runtime was built from the ground up so that everything is non-blocking and the language has built-in su
146.
▲
by
sreque
9y ago
I can only guess, but it is in general very difficult to retrofit what is essentially green threading, coroutines, and continuations into a runtime that was built without those features. Scala has tried at least a couple of times, and as is
147.
▲
by
sreque
10y ago
In my opinion, functional programming, like most programming terms, including object-oriented programming, means very different things to different people. For example: 1. The LISP family of languages encourages a style of functional progra
148.
▲
by
sreque
10y ago
I would recommend the stairway book and the coursera course. I would also steer away from the some of the other recommendations posted here, including "Functional Programming in Scala", which are basically teaching you how to writ
149.
▲
by
sreque
10y ago
Good point, but I don't think it's necessarily incorrect to conflate organizational concerns with architectural concerns. I am reminded specifically of Conway's law: https://en.wikipedia.org/wiki/Conway%2
150.
▲
by
sreque
10y ago
I think the article is missing a key value of microservices, or at least smaller services: service ownership. With a monolith, who is on call for the service when something goes wrong? How does that person find an appropriate person to diag
More ›