Re: [dev] What is bad with Python

2014-03-04 Thread Silvan Jegen
On Tue, Mar 4, 2014 at 4:59 AM, Zack Breckenridge wrote: > All language issues aside, I think one of the things (that others have > touched on here but I'd like to reiterate) that makes something > suckless is fewer dependencies and less version management. > > Due to Python's "batteries included"

Re: [dev] What is bad with Python

2014-03-04 Thread FRIGN
On Tue, 4 Mar 2014 09:14:05 +0100 Silvan Jegen wrote: > I have been using Python for a few years and never had any version > management issues. I assume this was because I use it for simple > scripting where mostly the standard library was needed which is > actually an argument for the "batteries

Re: [dev] What is bad with Python

2014-03-04 Thread Manolo Martínez
On 03/04/14 at 07:49am, FRIGN wrote: > On Tue, 4 Mar 2014 09:14:05 +0100 > Silvan Jegen wrote: > > My biggest gripe with the language is the absence of static type > > checking at compile time. > In some cases, Python is up to 50% slower than well-written C, but to > be fair, it does the memory

Re: [dev] What is bad with Python

2014-03-04 Thread FRIGN
On Tue, 4 Mar 2014 10:18:02 +0100 Manolo Martínez wrote: > I am not a programmer, but I write code in scientific modelling. Python > + Numpy + Scipy (which, I understand, takes care of typing in a > reasonable manner) is plenty fast, and very readable (and writable). No wonder, given Numpy and S

Re: [dev] What is bad with Python

2014-03-04 Thread Manolo Martínez
On 03/04/14 at 08:37am, FRIGN wrote: > No wonder, given Numpy and Scipy are mostly written in C and Fortran ;). That is true. As an aside, apparently Julia scientific ibraries are mostly written in Julia, which makes me wonder. > Moreover, from what I understand, you actually use special types >

Re: [dev] What is bad with Python

2014-03-04 Thread FRIGN
On Tue, 4 Mar 2014 11:05:54 +0100 Manolo Martínez wrote: >But I haven't experienced any maleficency yet :) I probably haven't chosen the right words for it. I referred maleficency to the breaking of language-conventions, because you handle those special types. Quite similar to what you can see w

Re: [dev] What is bad with Python

2014-03-04 Thread sin
On Tue, Mar 04, 2014 at 09:25:26AM +0100, FRIGN wrote: > A question to everyone on this list: What do you think about the > Go-language? I have no experience with python, but I use golang a lot. Lua is also quite fun to code in.

Re: [dev] What is bad with Python

2014-03-04 Thread psepheroth
I use python. But only less often. The last time I use it is when I tried processing txt files contents which includes string manipulations, regex matching, etc. On Tuesday, March 4, 2014 7:51 PM, psepheroth wrote: I use python. But only less often. The last time I use it is when I tried

Re: [dev] What is bad with Python

2014-03-04 Thread Silvan Jegen
On Tue, Mar 4, 2014 at 9:25 AM, FRIGN wrote: > A question to everyone on this list: What do you think about the > Go-language? I used Python for all my scripting needs before Golang hit version 1.0 (around two years ago). After giving it another look then, I have come to prefer it over Python. Th

Re: [dev] What is bad with Python

2014-03-04 Thread FRIGN
On Tue, 4 Mar 2014 14:27:26 +0100 Silvan Jegen wrote: > I am quite sure I would find more issues with Golang if I would be > writing more substantial programs but until then I will be happily > coding more in it. Well, what I noticed is the huge size of the compiled binaries. 2.2M for a "Hello W

Re: [dev] What is bad with Python

2014-03-04 Thread Andreas Krennmair
* Silvan Jegen [2014-03-04 14:30]: * There are no generics (it is not clear at the moment whether they will be incorporated into the language in the future) but with my simple requirements I have not been missing them. They will be incorporated as soon as someone finds a good solution to this

Re: [dev] What is bad with Python

2014-03-04 Thread Strake
FRIGN wrote: > You can write beautiful and readable code in any language. [assuming that "you" means the reader in general, not S. Jegen in particular] False. I can't write such code in MATLAB, for example. > A question to everyone on this list: What do you think about the Go-language? I'm not

Re: [dev] What is bad with Python

2014-03-04 Thread Bobby Powers
Hello, Strake wrote: > * Member selection is in some cases cumbersome, in which it would not > be in C, which is related to ¬(variant types) Can you explain more what you mean? yours, Bobby

Re: [dev] What is bad with Python

2014-03-04 Thread Nimrod Omer
On Tue, Mar 4, 2014 at 12:25 AM, FRIGN wrote: > A question to everyone on this list: What do you think about the > Go-language? I'm afraid to ask: what do you think about the Rust language?

Re: [dev] What is bad with Python

2014-03-04 Thread Zack Breckenridge
> I'm afraid to ask: what do you think about the Rust language? Personally, I mostly really like Go. But I would say one of my biggest problems with Go is (as far as I know) forced Garbage Collection. Depending on your point of view, that's either a strength or weakness of the language. From what

Re: [dev] What is bad with Python

2014-03-04 Thread Szabolcs Nagy
* Silvan Jegen [2014-03-04 14:27:26 +0100]: > On Tue, Mar 4, 2014 at 9:25 AM, FRIGN wrote: > > A question to everyone on this list: What do you think about the > > Go-language? > > I used Python for all my scripting needs before Golang hit version 1.0 i hear this a lot and don't quite understan

Re: [dev] What is bad with Python

2014-03-04 Thread Zack Breckenridge
On Tue, Mar 4, 2014 at 12:56 PM, Szabolcs Nagy wrote: > * Silvan Jegen [2014-03-04 14:27:26 +0100]: > the heavy python runtime has unspecified interactions ... > go is not very good for either of these: it cannot directly > interact with anything written in c (it has a hack (cgo) ... I would s

Re: [dev] What is bad with Python

2014-03-04 Thread Silvan Jegen
On Tue, Mar 04, 2014 at 08:56:18PM +0100, Szabolcs Nagy wrote: > * Silvan Jegen [2014-03-04 14:27:26 +0100]: > > On Tue, Mar 4, 2014 at 9:25 AM, FRIGN wrote: > > > A question to everyone on this list: What do you think about the > > > Go-language? > > > > I used Python for all my scripting needs

Re: [dev] What is bad with Python

2014-03-04 Thread koneu
On 03/04/2014 09:23 PM, Zack Breckenridge wrote: I would say these are both pretty good indictments against both languages. So what are some preferred alternatives? I like Squirrel[0] and Solid[1] alot. Both of them interact well with C. The Solid runtime is written in pure C, so it is the prefe

Re: [dev] What is bad with Python

2014-03-04 Thread Szabolcs Nagy
* Silvan Jegen [2014-03-04 21:30:47 +0100]: > On Tue, Mar 04, 2014 at 08:56:18PM +0100, Szabolcs Nagy wrote: > > dont expect fast opengl access from go) and you cannot really > > use it for quick scripting tasks > > Why should Go not be suited for quick scripting tasks? I use Go to parse > text f

[dev] [st] [patch] solarized color theme

2014-03-04 Thread Michael Hauser
Hi, I just made my first patch with help from friendly irc users. The applies the solarized color theme found on: http://ethanschoonover.com/solarized to st. Cheers, mih -- 'aware water' is an anagram for 'we are at war' diff -up st-0.4.1/config.def.h st-0.4.1-solarized/config.def.h --- st-0.4

Re: [dev] What is bad with Python

2014-03-04 Thread stanio
* Szabolcs Nagy 2014-03-04 20:57 > […] thanks you cared to explain --s.

Re: [dev] [st] [patch] solarized color theme

2014-03-04 Thread Christoph Lohmann
Greetings. On Wed, 05 Mar 2014 06:51:49 +0100 Michael Hauser wrote: > Hi, > > I just made my first patch with help from friendly irc users. The > applies the solarized color theme found on: > http://ethanschoonover.com/solarized to st. Thanks for the patch. Please add it to the wiki. Sincere