gtycomb

It is here in HN that I first heard Pablo Neruda's "No culpes a nadie". Even though a fan of Neruda I somehow had missed this. Perhaps this speaks to you something too:

        ## Don't Blame Anyone

 Never complain about anyone, nor anything,
 because basically you have done
 what you wanted in your life.

 Accept the difficulty of improving yourself
 and the courage to start changing yourself.
 The triumph of the true man emerges from
 the ashes of his mistake.

 Never complain about your loneliness or your
 luck, face it with courage and accept it.
 In one way or another it is the outcome of
 your acts and the thought that you always
 have to win.

 Don't be embittered by your own failure or
 blame it on another, accept yourself now or
 you'll keep making excuses for yourself like a child.
 Remember that any time is
 a good time to begin and that nobody
 is so horrible that they should give up.

 Don't forget that the cause of your present
 is your past, as well as the cause of your
 future will be your present.

 Learn from the bold, the strong,
 those who don't accept situations, who
 will live in spite of everything. Think less in
 your problems and more in your work and
 your problems, without eliminating them, will die.

 Learn how to grow from the pain and to be
 greater than the greatest of those
 obstacles. Look at yourself in the mirror
 and you will be free and strong and you will stop
 being a puppet of circumstances because you
 yourself are your own destiny.
 
 Arise and look at the sun in the mornings
 and breathe the light of the dawn.
 You are part of the force of your life;
 now wake up, fight, get going, be decisive
 and you will triumph in life. Never think about
 luck because luck is
 the pretext of losers.

I wish I could give you a thumbs up for speaking plain truth here. Anyway programmers will find out for themselves how best to satisfy their customer need.

In addition to your list here, I am drawn by ES6 on the backend. This is not javascript of the early days.

On Differentiable Programming, you might be aware of a tensorflow counterpart in javascript:

https://www.tensorflow.org/js

I tested this to a certain extent and its not a toy. Its well thought out product from a very talented team, and has the ease of coding that we love about javascript. It can run on browsers!

This being said, we should note the strengths of a statically compiled language with the ease of installation and deployment like with Go, Rust, Nim, etc. in enterprise scale numerical computing.

Nim is a languge that has good performance and I had good experience porting an enterprise Python application to Nim (for performance gain). For a new user the risk obviously is the newness of Nim but the Nim team was very helpful and prompt whenever I posted a question. Its a very complete and surprisingly issue-less language.

Hopefully Arraymancer will help increase its reach, I wish the implementors all the best.

OP likes Swift and he compared it to other languages Python, Go, C++ & Rust, Julia. In the enterprise sphere that I am in, I haven't seen Swift and its hard to move a team in this direction at this point.

Python already drives a significant market and captured talent in numerical differentiable programming, particularly because of the ease with which prototyping and tuning is done with it. Obviously when we want to scale we have the conversation on some other option.Personally its a bit frustrating that Go support for TensorFlow or one of the competitors is not quite satisfactory and this is surprising, I can't explain it.

Instead of inventing any new language why don't one of you -- Python, Go, C++ & Rust, Julia, or Swift -- complete the job with end-to-end differentiable programming. 'Complete' to me means a language level seamless GPU (or related distributed/parallel architecture) and language level deployment ease (the kind of thing done with Kubernetes) and integration with embedded hardware.

Written form please. This saves time in many ways, such as searching for certain chunks of information when trying to form an early opinion on how this product fits one's need. I went through your dev documentation today and the organization is good. I wish you would present the more detailed booking example in the same conversational style as the shorter hello world example at start. When a developer sees the first page with the bullets of interesting features (service discovery, load balancing, etc), they would want to get a broader picture of the architectural approaches combining these features (through coding examples). Interesting work. Thanks for creating it.

Isn't it Go?

I don't miss generics either, not in the least. The interface system, Go's particular approach to it, takes me a long way ...

I won't ask for any new feature for today or tomorrow. But for day after tommorow, within a longer time research horizon, I wonder whether compiled and distributed Go applications can be made to interact along the lines of interfaces within an application now. May be its my struggle with Kubernates (as a newbie) that makes me want: Can there be secure language mechanisms supporting clustering, scheduling etc in a distributed enviroment with an external agent armed only with prior package interface definitions of a deployed Go application.

Please don't sacrifice performance, and fast compilation times. That module system is looking good!

Favourties: > Worked on most of the Go standard library. Primary author of net/http, database/sql, os/exec, Go's build/test CI system, etc.

Thank you. Software poetry they are to me.

And this one: > met Googler wife

Best wishes, Brad Fitz

I am an average Go programmer, so I may not be deep into Go as you might be. However the mention of GOPATH catches my eye. All my issues with GOPATH went away for me when I started using the Go Modules: https://blog.golang.org/using-go-modules. Also Go's approach to err is one the reasons I started gravitating to Go -- my old Go code is more readable because of the verbose (error as strings in my code) and hence easier to maintain. Go is a surprisingly practical language for distributed, system oriented, undertakings I'd say

At least those who do, want to learn because they can build cool things they can show off to friends.

I have no doubt about what you say. I had a really broken laptop that my 3rd grader happily tookover as his laptop, a linux machine mind you, about which he knew nothing about. I showed him how to open a terminal and use some bash commands, and how to invoke the Python interpreter and import a turtle graphics module. He was hooked and had lots of fun moving the turtle around (along with the incentive to learn some math at his level). I remember the day he walked to school with this duck taped laptop on a show and tell day, which ended up with the school's IT departement making Python available on all computers in that elementary school lab. I don't think he could have pulled this off in lisp. Beautiful language Lisp,but I don't see how I could have helped with graphics programming within an hour or so -- which was all what he was interested in.

started a project of deploying kubernetes cluster at home and hosting

I am also thinking along these lines but not sure about reasonable paths to try. Care to share some pointers on your setup? Basically looking to serve web pages from a server cluster at home.

Similar to books, growing up in India I discovered “Western” music because of pirated music. The one and only reason I heard of bands like Yes, Jethro Tul, Roxy Music, Steely Dan, Dylan, Joni Mitchell, or St. Martin in the Fields, etc. are the pirated copes moving from hand to hand among our school buddies. There was no way we could have afforded the orginal copies from the publishers.

Well the clocks ticked, I came here for graduate school and but the time I got my first job, over a period of time I had instinctively purchased all the original CDs and Box Sets of these and many other artists, about 1000 of them on my shelf. When I exchange notes with with my old buddies, some in Canada and some in England, they have more extensive collections than me. For one weak immitation of a Gibson lookalike guitar we had, we own a small stable of the real things by now :-)

The pirated copies that hooked us to the artists in the first place. I hate to steal from the artists I so much adore, but then shouldn’t there be a way to spread the music around.

Link to a slide set in this distribution -- the overall approach.

https://docs.google.com/presentation/d/1cF7qFtjAzkXL_r62CjxB...

A beautiful piece of work. What else to say.

A piece of jewel. Reminds me of chalk board talks of Gilbert Strang and Robert Gallager (also on youtube, mit video lectures) that celebrates this gift for teaching us something.

Consider that fact that prime-minister of Singapore knows Haskell by now

http://wadler.blogspot.com/2015/04/prime-minister-of-singapo...

He is already quite good with C++

https://arstechnica.com/information-technology/2015/05/prime...

Hope we find a way to vote some of them out fast.

Some months before the last big bail out legislations, in my state we had a US Senate candidate who was new in our political scene, appeared as a local man with a law degree from our state university, and he spoke about how the working people struggled with unemployment, delinquencies etc, as he knew middle class issues and can change the ways of Washington. PBS featured him and I still remember the interview they aired from his kitchen in a middle class home. I am among the people who voted him in.

A few years after this election I checked his voting records by chance and I realized that he had voted almost always in favor of the bailout system. I wouldn’t have known this by just reading the news or watching cable. In the next election cycle he won handily, this time supported by organizations with cash to blanket our news with favorable lines for him. That’s how life works I guess.

Politicians are not at all stupid in general. The problem we have is in their selective listening after we elect them.

If a legislator is not technically up to speed, considerable tax payer money goes towards hiring people in government to do the research and the explaining. Some high level advisers may come from organizations with a private agenda and after a few years of working within the goverment these experts pop right back to their industry jobs and we don't hear of them anymore.

Ultimately its the same need in whatever form of government we want – we need people we can trust.

more than that, I'd say. The young auto-rikshaw man on my way to the bus station from those gates was telling me about his kidney disease and how those sisters helped raise the substantial money for a transplant ...

Recently I was in India and certain circumstances connected me with a facility for the elderly run by an order of Catholic Nuns. I visited them quite a few times and while inside those closed gates there was this sense of reverence, peace, and shall I say holiness in many ways truly tangible. And when they bid me goodbye at the main gates, even as we stood there chatting a little while, the town or village people walking by outside the gates would smile and one of the sisters would call out to ask something about them. These sisters were involved with this outside world, and knew them and their needs so intimately! Yes, there is so much to understand about these areas of life us software engineering types seldom think about, it seems.

I heartily wish that you continue learning Rust, another significant contribution to open source languages. What has been already commented, things such as borrow/checker are humps you work through and it will work out for you eventually. The other challenges are some of your enterprise 3rd party integrations with the outside world, some of which may again demand your time if they are still in beta, etc.

Also, the organization has no desire to invest in training or experimenting. The project is funded by the "business" and they want to see a business result in return for their money ... so you basically you sneak in a bit of time as you try/test something new. Nim won out by somehow getting a team with python expertise learn and deploy their product fast enough.

When I started an enterprise data project with a small team where Python was the familar workhorse we stopped for moment initially to think of ways to improve performance. Cython was the familiar route with Python but we started building small prototyes in Rust, Go, and Nim. Beyond the basics our progress slowed down with Rust and Go (yes, I know Go is very easy for some) but Nim allowed us to put together a fully fairly complex application in short time. Just one book, 'Nim in Action', gave us all the ropes, every example in it worked (thanks Dominic), and some of our key integrations such as Postgresl Client drivers, built-in web UI (Jester) framework, Json processin, Nim's build/packaging support, generics, fast static typechecking, etc were exceptionally robust (for this young a language) and worked in an intutive way for us ... we reached production rather smoothly.

What is it about software development that keeps on attracting these "methodologies"?

Here is one data point for you from personal experience. A few months after got started at a US company operating in about 30 countries (primary business is manufacturing in the Casino and gaming industry) the word came from the CIO that I implement Six Sigma as part of the enterprise architecture activity that I headed. I countered that neither software engineers nor the IT architects and admins worked in the Six Sigma way and wondered at the meeting where this whole idea came from. I was told this was what the Chief Operating Officer and/or VP of Finance wanted to implement "across the company". Such things happen in this world we live in.

This Labor day weekend I took my old Nikon D600 DSLR on a visit to a State Forest nearby. Usually I go with no camera, I like to have my hands free to look around while my family takes snaps with iPhones which is enough. However back at home this week we are all still looking at the pictures from the D600 and struck by the picture quality -- the details of how they capture light, interesting compositions on a good standard wide to zoom lens, etc. I'd say that the weight of the camera is not a bother if I have to carry a camera at all.

This body of knowledge taught to us from early 1960's onwards is remarkable, they accomplished so much in the world. Clever 'graphical' algorithms like Karnaugh Maps that subsume more theoretical structures such as Boolean Lattices are a delight

'Topics In Algebra' by I.N.Herstein. Back in college years this was my first book. Despite many other books (which might look easier) I always came back here because of the care it takes to walk through well crafted progression of concepts. (Not a 'computer science' book but you will need something like this for the Algebra part)

There may be something to what you say, speaking of newer generation fashion busineess that try a newer technology. As an architect in this area during one phase in my career, numerous fashion heavy weights ran SAP gobally. Oracle too must have a good footprint.

fashion/media centers like NY have their own buzz even in technology. I remember back when Scala appeared, even Wall Street Journal running an article touting Scala as the next big happening in technology.

Thanks for mentioning, I didn't know of this. A classic Python module it is, sweet and simple.

In the early 1980's in addition to Smalltalk, the precursors of Haskell such as Hope, Miranda ... Byte would bring us these research languages and one would jump in and try them out.