Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Skyrunner]

And of course AMD's CodeXL debugger won't work for me.

Mainly, it's unable to step into kernel code, despite the fact that that's the entire point of it.

[gogis]

Its a list of what you should know as a CS Major, NOT as a Software Engineer. It also doesn't say you'll need it, it says you should know it (big difference, you should know lots of things you don't need to know)

The document is intended to position you to seize basically every opportunity that comes along, from my reading. Vim is a useful tool for that. Nothing on this page is mandatory to be a successful software guy, even a senior guy. Everything on this page is useful as a tool in your arsenal for getting there and will help you take advantage of opportunities along the way. Vim and Emacs are both ubiquitous across unix-based systems, and they are one of the more common bits of technology among organizations that use them - learning them is definitely a useful thing, and I've got no problem with them appearing on this list. They also encourage a mentality that is useful for Computer Scientists even if they don't end up using them in their job BECAUSE they don't just hand everything to you, but expect you to use it as the base of a tool customized to fit your needs. The document emphasizes in multiple places how important it is to do things from scratch at least once, understand how and why the pieces fit together and fit them together yourself. Something like Vim is an extension of that and useful to know. He makes it quite clear that you're learning it to familiarize yourself with the philosophy, not because of it's usefulness. Even if you don't adopt the Unix philosophy yourself, familiarity with it is extremely important if you want to keep doors open moving forward.

It's not needed and I don't think the document says otherwise. Much like learning Racket, it's about the benefits of learning the tool rather than needing to use the tool moving forward.

I really, really can't argue with you, because my english sucks. I can write a novel in my original language about how this article is wrong on many levels, but I disgress.

On a foot note, overall, it's a terrible document for anybody who is going for practitioning programming. I mean real job. If you ever is going for senior position in a software company - it's a bad reading. I mean it - it's harmful and you will be dissapointed in the end. It's good theorethically, but otherwise stupid. I dont even want to start to talk about how business needs is important in practical programming. And this is totally absent there. And I am generally adamant about how education system is bad for real job needs, but it's a whole new topic worthy.

Sorry, I was folllowing this thread from start, and I really was taken away just by this exact text. So I thought I should answer, whatever crude my answer was. And gosh, vim vs IDE is last subject which matters, please stop it, I am already bored.

[Mephisto]

Just about every other post, I mention my job. Sorry about that, but it's the least bad job someone like myself can have. Python and Django, what's not to love?

Anyway, I was introduced to the lovely pile of WTF that is classic ASP a few weeks ago. You see, this wasn't always a Python shop. Their old url rewriting code is in ASP.

Url rewriting. Classic ASP. You can probably see where I'm going with this.

For those that don't know, I'll clue you into my understanding of how this particular implementation works so far.

1. Navigate to url with a GUID at the end of the path
2. Server throws 404
3. index.asp catches 404 and does mangling
4. index.asp does second pass of mangling
5. index.asp redirects to the final destination
5a. If there was a file, redirect to the file
5b. If no file was found, serve some "this file was not found" text

What does this mean to the user? 404 OK, 200 Not Found.

[lue]

What does this mean to the user? 404 OK, 200 Not Found.

That's hilarious and terrible at the same time. I hope those are the only redefinitions.

[Siquo]

[deleted, I'm not being constructive]

[alexandertnt]

So I thought I would look at using SFML, as an alternative to SDL. Is there something I am missing about 3d vectors, or is SFML bugged?

Code: (C#) [Select]

Console.WriteLine((new Vector3f(1f, 2f, 3f) + new Vector3f(10f, 20f, 30f)));


[Vector3f] X(11) Y(12) Z(33)

 

Code: (C# (from SFML source)) [Select]

public static Vector3f operator +(Vector3f v1, Vector3f v2)
{               
    return new Vector3f(v1.X + v2.X, v1.Y + v2.X, v1.Z + v2.Z);
}


[cerapa]

LOL.

That's a pretty bad bug.

[dreadmullet]

Hahaha. I've made that mistake myself countless times. Just a typical copypaste error. What version of SFML are you using?

[Siquo]

So I thought I would look at using SFML, as an alternative to SDL. Is there something I am missing about 3d vectors, or is SFML bugged?

Oh wow that is pretty bad...

SFML is fine, mostly (although I currently use it for 2D)...

[alexandertnt]

Its being used for isometric graphics, so 3d positions and 2d graphics.

Im using the offical .Net bindings, 2.1 64bit.

Also, why on earth is Vector3f located in the Audio namespace

[Siquo]

That's odd...
I only used the C++ version... Where it's properly in the sf namespace: http://sfml-dev.org/documentation/2.0/classsf_1_1Vector3.php

[GalenEvil]

Wow, can you override that operator to fix it?

[MorleyDev]

The official bindings aren't written by the main developer of SFML, they're more "unofficial but officially endorsed" bindings...whoever did them probably put Vector3f in there because it's only used by SFML for 3d audio.

[Skyrunner]

Time to try to use C# for a quick and simple simulation*!

*hopefully I'll actually finish it within a few days

[alexandertnt]

whoever did them probably put Vector3f in there because it's only used by SFML for 3d audio.

Yeah, thats why I diddn't want to fix it, incase fixing the bug broke the audio system.

I just duplicated it, fixed it, gave it a new name, and put in some explicit type conversions to Vector3f's. Its all good now. Isometric graphics are now displaying properly