killertypo

cough borland cough :) Oh I guess, i just felt it was strange that Cincom still charges a significant amount of money to run their stuff, per seat and per server pricing.

When you look at the market of tools today. Historically speaking, they were par for the course.

Oh I do want to add that it is a language behind a paywall as well. Which i find rather strange. Being charged as a customer to one) use their language and two) being charged per user we allowed into the environment.

Because Smalltalk is an enclosed runtime (similar to Java, but much worse). We had to tell them how many users would be using non-developer editions of the runtime and they charged us for that.

I worked in a Smalltalk shop, smalltalk is not that great. I've discussed it at length, my problems with it. As a language it is impressive what they built at the time. In practice it was a terrible pain in the ass with tons of "ravioli" code everywhere. The language has no qualms with letting you wreck havoc within the standard base classes, which makes integrating anothers code almost impossible.

sounds angry and a bit self entitled. You and hundreds of thousands (if not millions) are using google services. To think that you are anymore entitled than the next guy (because you pay a nominal fee for a service) is a bit self centered.

Go is pretty new and pretty dang high on that list. Which is nice to me. It also makes me want to give it a shot in a project. Are there any nice templating frameworks for Go - that would be pretty much the only thing to prevent me from using it. I need templates like I do in Django.

this supports PUSH and POP

so you could easily PUSH the current node

dive deep deep deep deep (and even have no problem adding more later)

then POP the original location back.

true and it does suffer from deadlocking (which the author states is a possibility, if one thread never releases the mutex)! Either way, it is a very lightweight implementation and Rust does shine here.

I am referring to third party tools https://code.google.com/p/go-wiki/wiki/PackageManagementTool...

It would be nice to have it baked in, but thus is the life of bleeding edge development (of which I do not engage, in my safe Python Cocoon).

Thanks! I would much rather prefer being forced to specify a version than not. Consider building with more than one developer in mind. Or a developer joins the team a year down the road. Why waste anyones time not taking a moment to say "no we need v.1.1".

Good to see none the less!

TIL.

A painfully simple logger that makes use of Rust language features to ensure that it's allocated only when it is used, is RAII safe, and is mostly memory safe.

A lot of boilerplate C or C++ code was eliminated, and while we never see the actual assembly, we're told that it would generate similar instruction sets to the C C++ implementations.

So we should get pretty good performance out of it!?

Much like Go! i'm not a big fan of languages whose includes are managed as such:

    [dependencies.lazy_static]
    git = "https://github.com/Kimundi/lazy-static.rs"

Does Rust, like Go, have tools for freezing dependencies? So when the git project changes, you're not left wondering why a project has sudden bugs not seen before?

I love the idea of how easy these can be included in a project, but I dislike leaning on a public repository that may change at a moments notice.

For as much as I hate Maven for some reasons, I do appreciate the ecosystem and the ease at which I can...say, ask for a specific version of a specific artifact - ensuring my application will always build.

I always try to explain that pixel perfect just isn't feasible when we're going across platforms browsers and devices sizes / types.

If they would like to create 20+ different mockups and supply them to me I'll gladly do it for an exorbitant sum money, but otherwise they need to realize that the relative fluid nature of the web and it's many form factors is going to preclude them from getting that pixel perfect design.

Then all of that flies out the window because we have that one asshole manager who promises the world and ensures it will be delivered yesterday :)

Yes and no, it depends, If you use the entire suite of bootstrap, yes. We did not, we used it for the grid system (getting those nice big perfectly sized columns). Everything else was hand written CSS and HTML.

Is there any particular reason? Requiring support for older or legacy browsers?

I just recently wrapped up a project utilizing customized Twitter Bootstrap / CSS3 / HTML5 and I was pleasantly surprised at how smooth everything went between IE/Chrome/Safari/FF. This is the first time, in a long time, that everything just "worked."

Congratulations on 1.0 but these kinds of buzzwordy lines

    Accomplish in 10 lines what would otherwise take 1000,
    thanks to a reactive programming model that extends all 
    the way from the database to the user's screen.

Really bother me.

Show me where you eliminated 1000 lines of code and how it was beneficial. Each line of code, to me, is placed with purpose and intent.

Are you eliminating thousands of lines of boilerplate? Or are you making best guess assumptions that fit the common need, and we still end up with those 1000 lines for something truly custom?

and when you kill the process and restart it, it will gladly restore your session and the memory will be in a better state. It will still degrade, but for a short time it's going to be awesome with all of those tabs until the leaky memory finds its way back into your browser.

i almost have to buy one or two or three on principle alone.

So our answer has to just been to hire more developers, more and more and more developers. As the complexity grows, so does headcount.

This is why I thank the stars that I am the opensource developer, focusing on linux / Python / Django development. I cross over into SharePoint only when we begrudgingly use it as a CMS for a windows 8 app or similar.

There is an effort now to write an external service bus to manage a lot of the business logic complexity that we've baked into SharePoint. With the eventual goal of having SharePoint and other resources leverage this SB and use it instead.

this makes sense, i work in a pretty convoluted SharePoint environment. It is completely impossible to spin up a development environment without dozens of scripts and knowing exactly what lists to manually create and what data must be present inside of them.

This means that new-hires are handed a cryptic and seriously out-of-date document with instructions on how to setup a proper VM environment.

They check out their code.

They deploy...but wait the deploy fails because of missing data, missing document types, missing lists...

Open up SharePoint, enable some doc types not turned on by default, turn on some more features, add a list. Deploy again, no wait it died again, oh now it's a different doc type and a different feature that the deployment doesn't turn on by default ...etc

The end result is a mess that requires days to get up and running, not hours.

My niece will write songs or letters and has even written lists of things she doesn't like that her parents do... She usually shares it with grandma before going to her dad about it.

what happens when `do_small_thing_one()` gets changed enough that the name of the function is no longer representative of the code? Comments and method names can fall out of sync. Comments at least require less to update and don't require re-factoring code in multiple places.

I don't buy this at all. My iPhone 4 simply will not bend no matter how I flex it. My Brothers Note 2 does not bend, though I can apply some force and get a little bend out of it, it bends nothing like the iPhone 6 Plus. So while this article is free to "Duh" me all it wants. Simply put, standard wear and tear should not ruin/bend/crack the phone. Apple knows that people put these things in their pockets. I don't agree with putting phones in the back pocket, hell that's just asking for trouble (sitting on your $300 subsidized phone? lolwut), but this reportedly happens in the front pocket as well.

There are some great videos of iPhone 6 pluses being bent with little force (comparably to note3 phones).

Also I can't even fathom folding an iPad into the debate. I don't know anyone who puts theirs in their pocket. Maybe if I actually stepped on it (which happens as my daughter likes to leave the iPad laying about wherever she finished using it last, sometimes in her blanket forts).

improve gravity and friction, a bit too floaty and the lack of friction means i can pull out entire mid sections in one fell swoop without loosing the tower.

put a donate button on the site, seriously - for those one to two times a year!

Not if you override that bit of logic in the system. Cars are reprogrammed all the freaking time - for performance reasons.

It's not very far fetched to do the same for other nefarious reasons.

if your job is providing security and GOOD security relies on GOOD entropy i fail to see the issue...

Sounds like it was written by my dad

Because this author does not like Node.JS apparently. Like I said, I would love to see some examples that clarify what the writer is intending us, as his audience, to learn.

I am always interested to hear what people do not like about a language, and I think it says a lot about what they really know.

I get the point of this article...but it is a bit bland, short, and doesn't really offer much in the ways of why this is dangerous or how it applies to the average Joe.

Maybe with some more meat this article would be a big selling point; however, right now it offers, what may be a completely valid point, masqueraded behind a very thin veil of, "Because others say so!"

Tell me why!! Give me an example. Show me how Node.JS fails at distributed concurrency because it is an over-use of it! :)

If you are seriously interested and worth your salt please reach out to me directly https://github.com/MikeMcMahon