Good vs. Evil

  • The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord
11 I mean things like put vs post and things like that. Maybe http would be a better way of phrasing it.
 
12 for most of the stuff you just need to know the difference between GET and POST requests. Its only when you are dealing with "RESTfull" api's that DELETE, PUT and sometimes PATCH come into play.
 
13. Yes indeed. This is a Forum Game @Liza Pendray; what I always do is have a quick read of the first post on the first page of the thread, to see what its all about and how to play. Its good fun!
 
12. Yes... whatever that means...
13 For reference, this is a program that should print hello world.
Code:
;Copyright (c) 1999 Konstantin Boldyshev <[email protected]>
;
;"hello, world" in assembly language for Linux
;
;to compile:
;
;nasm -f elf hello.asm
;ld -s -o hello hello.o

section   .text
  global _start       ;must be declared for linker (ld)

_start:           ;tell linker entry point

   mov   edx,len   ;message length
   mov   ecx,msg   ;message to write
   mov   ebx,1   ;file descriptor (stdout)
   mov   eax,4   ;system call number (sys_write)
   int   0x80   ;call kernel

   mov   eax,1   ;system call number (sys_exit)
   int   0x80   ;call kernel

section   .data

msg   db   'Hello, world!',0xa   ;our dear string
len   equ   $ - msg       ;length of our dear string
This is the same code in lua
Code:
print "Hello, world!"

As you can see, you need a lot more instructions when writing assembly. And this just writes some simple text in the terminal.
 
11 This class is going to be great. The study group for the class has had people post already that we should "[not] listen to $prof about not using for loops. At all. He's been doing it for years, and he's been wrong for years." Given the "don't program based on what the language provides" was in the part where he was having us implement an iterative algorithm recursively, I think it ties into this hatred of for loops.
 
9 Most of it seems good, but when you have things that are that wrong, it makes you suspect everything else too.
 
11 This class is going to be great. The study group for the class has had people post already that we should "[not] listen to $prof about not using for loops. At all. He's been doing it for years, and he's been wrong for years." Given the "don't program based on what the language provides" was in the part where he was having us implement an iterative algorithm recursively, I think it ties into this hatred of for loops.
10 my teachers also shove recursion into everything right now, but considering we are going to learn functional programming (I think) and we where learning about functions, that makes sense.

We also had the fun of working with functions that get functions as parameters and return a new one. Again, makes sense considering the topic, but I'm not sure how I would feel if I saw those functions in a real codebase.
 
9 It makes some sort of sense given the lecture was on systematic loop design, but he still ignores a lot of possibilities if they don't fit his "one right way". As far as the class goes, in my case it's a data structures class that starts off as a Java class, because the prereq is a python course, and they can't assume knowledge of Java.