Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
p0nce
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
70 ms
·
781.
▲
by
p0nce
9y ago
The new WebConfig library looks promising too: https://github.com/WebFreak001/WebConfig
782.
▲
by
p0nce
9y ago
None, since no customer ever asked for it. Much more people are asking for AAX or even LV2.
783.
▲
by
p0nce
9y ago
I'm making an audio plugin library in D, with the explicit goal to avoid all the pain of setting IDE projects, paths, and managing dependencies (all of this is done through the language package manager). https://github.com&#
784.
▲
by
p0nce
9y ago
Perlis's Epigrams are my favourite. http://www.cs.yale.edu/homes/perlis-alan/quotes.html "When we write programs that 'learn', it turns out that we do and they don't." I still wonder
785.
▲
by
p0nce
9y ago
Interesting. CUDA kernels are plagued by an explosion of entry points and OpenCL C kernels by the lack of meta-programming.
786.
▲
by
p0nce
9y ago
Well, it's true that they aren't good UI toolkits in D either (let's say as good as Qt). For me it works as the "everything" language, I also wrote CUDA bindings once (obviously that wouldn't work with mixed ho
787.
▲
by
p0nce
9y ago
It's the same old C++ rhetoric "only C++ can do it". Before it only C could do it, and before it only assembly could do it. Reasoning starting from conclusions to lead to initial constraints is backwards reasoning. For exampl
788.
▲
by
p0nce
9y ago
So: a C++ competitor shall beat it in every dimension you've choosen, until then it's futile to complain about the shortcomings of C++. This doesn't sounds very logical, only like a case of sampling bias.
789.
▲
by
p0nce
9y ago
> In what language can we have both? Have you actively tried to find one?
790.
▲
by
p0nce
9y ago
Don't think that cognitive biases don't apply to you.
791.
▲
by
p0nce
9y ago
> I don't know how CPU-efficient it really is though, foobar is pretty efficient. Here it handles MP3 decoding and spectrogram visualization with only a few percent of a CPU.
792.
▲
by
p0nce
9y ago
http://p0nce.github.io/d-idioms/#How-does-D-improve-on-C++17 ?
793.
▲
by
p0nce
9y ago
I use π for new kinds of projects and the golden ratio φ for well known types of projects. (edit: however, the only purpose of an estimate might be to go faster, so perhaps it's better to have an unrealistic one)
794.
▲
by
p0nce
9y ago
Also a task of finding what already exists.
795.
▲
by
p0nce
9y ago
My biggest complaint is how painful it is to change brush size and brush opacity.
796.
▲
by
p0nce
9y ago
So, it seems millenials are quite frugal after all, and previous generations aren't as much.
797.
▲
by
p0nce
9y ago
Burnout is a physical problem first and foremost, albeit caused by prolonged stress. (very interesting link: http://www.arltma.com/Articles/BurnoutDoc.htm )
798.
▲
by
p0nce
9y ago
It seems to me each DAW focuses on a particular problematic. - Ableton Live: focus on painless transition between live and written electronic music, quick producing - Reason: focus on modulating everything with a studio feel - Orion: focus
799.
▲
by
p0nce
9y ago
Hi, I make audio plugins. Let me know if you need OEM plugins for your DAW.
800.
▲
by
p0nce
9y ago
Yes the problem is with the grey area between recoverable and unrecoverable. .unwrap is only suitable for the unrecoverable case, while exceptions are suitable for both cases. Hence why .unwrap in examples is harmful imho.
801.
▲
by
p0nce
9y ago
See above where one user is using .unwrap for parsing errors (input errors are recoverable).
802.
▲
by
p0nce
9y ago
Exceptions are well suited for parsing errors because they embed an error message.
803.
▲
by
p0nce
9y ago
> panics aren't for recoverable errors, in any circumstances. And I understand that. Hence why unwrap everywhere is harmful.
804.
▲
by
p0nce
9y ago
> 2. If you have an invariant that you either can't (or won't) move into the type system, then unwrap/expect/panic'ing can be appropriate precisely because if that unwrap gets tripped, then that will indicate a b
805.
▲
by
p0nce
9y ago
That and the bizarre thinking that ".unwrap" is a perfectly ok thing to write in some cases (don't worry it will never make it to production!). No, ".unwrap" turns input errors into bugs, and there is no production
806.
▲
by
p0nce
9y ago
Hopefully some mechanism to handle exceptional cases at the language level will be invented soon.
807.
▲
by
p0nce
9y ago
It's harder in the office because it's a social group, the chatter may talk about you, your project, etc.. So the expectation is that you listen to it.
808.
▲
by
p0nce
9y ago
You can have people very happy about your product and still little to no "word of mouth" if your product is niche. For a niche product each happy user would have to tell many other potential user to make one conversion. So practic
809.
▲
by
p0nce
9y ago
Doing this very often. Abstracting the background noise and conversation is a skill that can be trained. It's even better in public libraries, because the noise is 10x lower than the typical open-space environment. You also make random
810.
▲
DConf 2017 Live Stream is up
(youtube.com)
1 points
by
p0nce
9y ago
|
0 comments
More ›